To read all comments associated with this story, please click here.
Hi,
So you're saying that the reason (some) web browsers don't bother complying with W3C standards properly is that they don't need to bother, because web developers will work-around issues anyway?
In that case, the only people we should be blaming is web developers. They should comply with the relevant standards (and nothing else - no browser specific extensions); and if a browser sucks dog balls that's the browser developer's problem and not the web developer's problem.
Instead of putting many extra hours into supporting a broken browser, do nothing, or just add a warning at the top of the page.
- Brendan
Edited 2013-01-06 01:57 UTC
I think web devs can use browser extensions, but should also provide un-prefixed versions of said extensions to "future-proof" their site.
This way you get the best of both worlds:
- You can prototype with many browsers
- You can implementations which are in a state of flux separate
- You are sure to support the unprefixed version when the standard is ratified and less volatile.
So for example if "StandardA" is finalized, you can use a prefixed version of it for say IE if Microsoft's implementation differs (say they implemented a Working Draft) and you can always keep the unprefixed version up to date.
The bigger issue imo is that these things need to happen faster. It shouldn't take years for a group of people to agree on things. It reminds me of the US Congress.
Well, following that philosophy would've meant that Microsoft would've put out more standards-compliant IE versions earier? Like before or around IE6? Right? Yeah, right.
While I don't like what Google has done here, it also feels very hard for me to not to laugh when I hear Microsoft, IE and standards in the same sentence, paragraph even. Yeah, I have a long memory, especally in topics that have left a lasting negative impression.
However, Google's goals of providing service for everyone is, and will always prevail over any kind of browser wars, since it's part of a much bigger picture than "just" browsers. So this hiccup will fade and they'll make the eventual - if any 0 IE-specific changes and go on.
Treat this whole issue as just a poke towards IE from one of its "friendly" neighbors





Member since:
2010-07-13
So as a web developer many hours extra are put into supporting IE. We only just stopped supporting IE7,and now you get a not supported/out of date browser warning. The web thinks nothing of that practice. The death of each new IE version is celebrated.
Perhaps, in the nice version, Google said we have been screwed over and over again by IE. But no more! Sure perhaps IE10 mobile is ok now, but in a year? When all the other mobile browsers move on?
Edited 2013-01-05 15:41 UTC