This has been entered into our database with the tracking number 4661. We've confirmed the issue, and will correct it in an upcoming patch.

I'm going to mark the thread as Resolved, as the bug is being worked on.


I work here