Linked by Thom Holwerda on Wed 25th Aug 2010 19:21 UTC
Permalink for comment 438362
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
More News »
Sponsored Links



Member since:
2008-12-29
There was me thinking the only reason was that all the stuff that wasn't implemented from 2.0 or was implemented incorrectly was dropped or re-speced to do what browsers chose to do instead of following the spec. (This comment applies to all browsers, not just IE). How to gain compliance 101. Redefine the specifications.
I will also question, but I'm not sure, as to whether they have a full implementation, or if as with CSS 1.0 they claim to have a full implementation but only support mandated sections and not optional parts.