Did they actually catch it in their own tests? Or is this an external developer catching it for them? I guess if it works, it works, but this certainly seems like something they could be testing for up front.
Did they actually catch it in their own tests? Or is this an external developer catching it for them? I guess if it works, it works, but this certainly seems like something they could be testing for up front.
I remember seeing it as an entry in Known Issues list of one or two beta releases. The final releases didn't have the problem.