I believe that has now been fixed in the latest build on beta and should be fine on retail as well, so I'm not sure if the workaround is needed anymore.