Did A Google Earth Mistake Cause A Couple's Brutal Murder?
Redditor Shamed After Girl Finds His Request For Her 'Porn…
Internet Explorer 9 -- on standards, interoperability, CSS3 and HTML5
IE9 will make great leaps in standards compliance -- but not simply by following the standards executed by W3C. Instead, they have analyzed real-world use to see which API calls to implement, to reduce the amount of code developers have to write.
In the keynote, they are now showing how Firefox, Chrome and IE9 all display rounded corners (CSS3) and execute addEventListener correctly. The same for opacity rendering, borders and radius, and so on.
As I mentioned in the previous post, you can play with all of these things on the IE9 'Test Drive' site.
And now our man is slandering Acid3 -- but they are quite intent to only implement features that are necessary, not just to get 100/100 in Acid3. Again, this is about developers and end-users, not just about pleasing the ever-critical pundits. Microsoft are working a lot with the community and the standards bodies, submitting standards tests to W3C to ensure HTML5 is a success (vested interest with IE9!)
Now they're on to GPU-powered HTML5...!
Comments
7
Subscribe to commentsjokermatt999Mar 16th 2010 12:59PM
Well...at least they're almost working at being standards compliant. Glad to hear they're at least implementing enough to pass acid.
AnthonyMar 17th 2010 12:47AM
They are NOT passing the Acid3 test. That's the thing. To pass the Acid3 test, a browser must score 100/100. To be suitable, they need to score at least a 90/100. Sure, it's nice that they are working to require less code. The problem is, though, that not everybody uses Internet Exploder. Sure, sites that are designed to work with IE will work well with Firefox, Opera, etc. However, developers will still have to write more code if they want their site to be standards compliant AND work with IE.
Rob StevensMar 16th 2010 1:23PM
"... but they are quite intent to only implement features that are necessary, not just to get 100/100 in Acid3. Again, this is about developers and end-users, not just about pleasing the ever-critical pundits."
This is the same backwards logic that got Microsoft to where they are now. By not supporting the full HTML5 spec from the outset, they're forcing developers to pick and choose which features to implement based on what will work on all browsers. They're not supporting what developers want, they're not-so-subtly forcing the developers' hand.
Why not support MORE, and force Firefox and Chrome to play catch-up?
Sebastian AnthonyMar 16th 2010 1:30PM
I think the problem is that Microsoft didn't design the Acid tests -- it's a fairly arbitrary selection of technologies, isn't it?
But yes, as long as they stick to the HTML5 standard, I am happy :)
SilverWaveMar 16th 2010 3:08PM
but not simply by following the standards executed by W3C.
'nouf said... oh wait...
FAIL!
PhillAholicMar 17th 2010 12:33AM
I think Microsoft is so far behind in standards that it's impossible for them to support it all at first. Firefox 3.6 gets a 92/100, so mozilla isn't supporting it all either. You have to give them credit. They are supporting HTML5 and CSS3. Three years ago I would have called you crazy if you said they'd be doing that.
JamesMar 19th 2010 12:06AM
Developers out there, back me up. A standard doesn't *count* if there's not a reference implementation, and you can bet your sweet bippy there's no reference implementation for correctly rendering CSS.