To view parent comment, click here.
To read all comments associated with this story, please click here.
The DOM issues are mostly browser specific problems.
You still have to battle beast of Redmond on a daily basis if you have to serve the public at large though.
Nice giant swaths of missing features...
http://www.findmebyip.com/litmus/
Especially the extremely useful CSS3 stuff.
But worse is its random bugs with canvas... yuck..
And with the latest version of IE for XP being IE8... Talk about random bugs... IE8 is the new IE6.
Thank god we don't have to deal with IE6 or IE7 as much anymore... IE7 was God's punishment for me complaining about IE6 for so long :-D
Somewhat related: if you want to make the world a better place for all us web-developers, spread the word that people stuck on IE7 or IE6 can install Chrome Frame without admin rights on their machines!
YAY: http://www.google.com/chromeframe
It won't break anything because it's only triggered if the website they visit specifically tells it to be enabled.
Maybe HTML5 will bring about world peace in another 5 years 
There is nothing wrong with IE8. Until Firefox 3.0 (I think) it was doing a better job of being Standards compliant.
Also what nobody mentions is that if you add an XML element to an XHTML document, every browser except IE will happily ignore that whether or not the namespace is declared at the top of the document or not, and render it even though it is invalid XML.
There is a lot of stuff IE gets wrong, but other browsers do lots of shitty things as well (until I think Chrome 12 or 13, if you were rendering a legend tag with display:block, it wouldn't render correctly unless you added a padding to the fieldset).
As for the missing CSS 3.0 features most of these weren't actually finalised or proposed by the time IE9 was beta. Chrome and Firefox have a very different release schedule than Internet Explorer and why there is always a discrepancy in features.
The problem with HTML V5 is...well...its a pig, it really is. Everyone is pushing it as a flash replacement but frankly I can open SD flash on even the 1.8GHz Sempron I keep at the shop for a nettop and the video is smooth, even without any GPU acceleration, whereas with HTML V5 I've found anything short of a dual core to be a slideshow unless you have a dedicated H.264 decoder onboard.
I have a feeling we are gonna look back in 3 years and go "Remember Flash? I really miss that" because unless they figure out a way to fix it HTML V5 not only supports just a subset of the use cases Flash did but it does so while sucking CPU cycles like a drunk sucks down a free mini-bar, its just plain awful.
Known bug... at least for Firefox.
https://bugzilla.mozilla.org/show_bug.cgi?id=495727
Given that it's been three years, I'm starting to wonder how one would get through to the Firefox developers that people are getting tired of waiting.





Member since:
2005-09-27
The DOM is partly fixed with HTML5.