Probably the best way is to open a bug report at
https://bugreport.apple.com/ . Apple will eventually close the issue with state "Duplicate /6448743". Unfortunately that bug report can't be viewed as it isn't public. According to their help page:
Duplicate:
+The reported issue is being tracked under the original bug number. You may check status of this issue by writing to ADC Bug Reporting.+
So the next step would be to email "ADC Bug Reporting" requesting a status update.
I too find it extremely frustrating that such a major productivity impacting regression is taking Apple so long to fix. It's even more frustrating that Apple is so non-communicative about it. I'd love to see an engineer working on the problem explain to this thread what the issue is, what it takes to solve it, and when we can expect a fix or workaround. It's the least they can do for us customers short of supplying us with a solution for the problem.
Message was edited by: Guido Kollerie (fixing spelling error)