IE 10 is a high quality standards compliant browser. Webkit rendering is not the web. You should support it. And Opera. And IE9 unless you absolutely require features it does not support.
You need a business case to write standards compliant accessible code that is browser agnostic?
WWW - as envisioned by Berners Lee - is getting worse.
> Berners-Lee identifies universality as one of Web’s key principles, providing people with the freedom to link to anything, regardless of hardware, software, or Internet connection.
I pay my rent with money, not with good intentions by some guy who has been granted a nighthood.
That said I assume a fairly standard webpage is rendered decently in Opera so I wouldn't block it (as I would haave done to IE if it had had the market share of opera).
I would say that the responsibility on the developer for that vision to occur is to write standards compliant code. Working around bugs or quirks in a specific browser I think falls into the realm of business case.
"Works in WebKit" isn't necessarily equated to "write standards compliant code". For organisations that manage to develop a website that requires a $100,000 outlay to work in Internet Explorer, that can't possibly be a web standards compliant code base they are starting from.
Webkit rendering is not the web, true. That's sad though. I'd rather it WAS the web, and we could go on and improve on it (new image apis, sound apis, acceleration, etc), instead of reinventing various variations of the wheel (ie. basic html rendering).
As for Opera, should they support any oddball browser engine out there with it's particular quirks?
