I don't think the underlying problem has to do with specific companies and applies to older versions of Firefox as well. The underlying problem is: (Demand\Rat

I don't think the underlying problem has to do with specific companies and applies to older versions of Firefox as well. The underlying problem is: (Demand\Rate of requests for specification changes) >> (rate of widespread implementation) ...ensuring there will always be a very narrow audience for the latest features. While it's good to increase the rate at which new specifications are implemented, it's largely impossible to do without authoritarian measures to A) control the programmers working on every web browser B) control specification committees to agree faster. edit: or C) make everyone use the same web browser Another approach is to DECREASE the rate of [edit: demand for] specification change. I think a large part of the problem is our expectations from the CSS specification. We are trying to expand its problem domain to include the construction of graphics and graphical effects, something which it was clearly not built for on a syntactical level! It might be better to convince browser teams with limited resources to better support long existing open standards to handle the dynamic creation of graphics with more logical syntax. Because the rate at which specification revisions are required will be drastically reduced. Whereas the process for creating new graphical features to your website via CSS is to submit it to a committee and wait 5years, it is done within the syntax of SVG. Making it a better allocation of resources.