If you notice, that particular item has no resolution or work-around.
How is one to read these release notes?
I have bugs (Leopard Java regressions) filed in radar that are not resolved, yet not listed in the release notes as "known issues".
What does that mean?
And for some of them, I've had to implement some hackish work-arounds when running on Leopard that I really don't want to keep in my app - while others have no work-arounds, and simply give my app a worse user-experience due to Apple's bugs.
For instance, problem 5993869, in which a modal dialog in Leopard Java would not disable menu items in the main menubar. So in a modal dialog, you can hit Cmd-Q - have the menu get highlighted as if you've activated the quit item - and have nothing at all happen! It didn't used to be this way on Tiger.
Another issue - 5739678 - incorrectly repaints a blinking cursor in text fields of certain sizes - causing visible problems. Again, a regression in Leopard Java.
Another issue - 5952212 - makes code-signing - a practice recommended by Apple for all new Mac apps - impossible if using Leopard's JavaApplicationStub.
And there's others.
Why are some things listed as "known issues" and others not - while still being opened bugs in radar?
Can't Apple at least acknowledge the existence of these bugs?
-Alexei Svitkine
