This bug is very interesting in light of some assumptions I was making. Need to investigate.
It’s great to see so much work going into workers and the tracing engine, though, and to hear that changes will start rolling out in point releases. I feel for corporate deployments, and I hate when it’s done through ever-present update services, but in terms of browser security and iterating/testing standards-to-be, this seems to be the release model to follow. It’s a huge relief to not have to work around Chrome 2′s Worker problems, and it will be interesting to see if something similar happens with Chrome 3 in the next month or two. But I worry constantly about Firefox 3.0 vs 3.5 vs 3.6.
I don’t have a clear idea of where the balance should be between AUTO-UPDATE and developers waiting 5 years for implementations to converge (or at least settle). “Make all things easier for the user” is a good starting ideal—as long as “declining our help” is first on the list—but the effect in aggregate would not be linear.
Rambling finished. Flash 9 it is.