You mean that Opera doesn't fully support standards
is what you mean.
My job at big river books is to roll this kind of dynamic stuff out soon. Right now our coverage is IE 6+ and Firefox 0.9+ and that's it. That's all I have resources to qualify. Given the bugginess of IE its been a lot of effort to get two browsers supported but the size of its user population makes it justifiable. I expect we will qualify Safari in the next couple months (it seems to "just work")and will expend effort to support that one too as it is the primary browser for a growing platform.
We do not expect to expend effort to make our JS work with Opera, Konqueror, iCab, or any other browser. We are checking user agent and simply vending non-js versions of stuff if a browser is not in our supported stack.
Word to the alternative browser makers and users. Make your stuff rigidly adhere to web standards if you want to remain viable - otherwise we will likely start putting links to supported browsers on pages you fetch with unsupported ones.
Its long past time for people to expect site developers to "support" anything but what is published at w3c.org. By the end of the year, I am expecting all non-legacy pages to pass validation at [link|http://validator.w3.org|http://validator.w3.org]. (Don't even try it on our homepage now - it is to cry to do so).
But talk of "supporting" buggy browsers is counter productive. The browsers should "support" us.
