Correct. Silverlight 5 is still in beta. They said that they had fixed the issue and will be part of a future release -- of a product that is currently in beta. You typically don't rush out fixes for beta versions of products.
You typically don't rush out fixes for beta
versions of products
Microsoft made a bold claim, people are curious about how they fixed Silverlight if indeed they did that. If not a new Silverlight release, than at least write some kind of blog post explaining what's different in Silverlight.
But I'd bet this is typical of Microsoft; right hand, meet left hand, please communicate :)
That might be relevant if it wasn't for the fact that Silverlight is not open source. They are under no obligation to show/blog their fix until they actually release. In fact, they would probably want to withhold it as long as possible if their intent is to damage WebGL.
Chrome does. Every time Ubuntu checks for updates (weekly or more often), there's a new version of Chrome dev channel available.