Thanks for posting.
Our Development department is aware of this issue but I don't have any further information at this time. For updates and a work around, I recommend viewing and subscribing to knowledge base answer #8080:
We're now approaching a month since this problem was identified. Is there anymore information on when a proper fix will be released?