Linked by Thom Holwerda on Tue 16th Mar 2010 16:54 UTC
Permalink for comment 413990
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/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
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
More News »
Sponsored Links



Member since:
2009-04-08
From the Ars article, it sounds to me like they still have a bad attitude towards compliance. The announcement of IE8 was the same story. Everyone said, "finally, they are listening" yet we're still writing workarounds for IE!
I understand little mismatches between browsers & OS's, but CSS3 should be a done deal. Like you said, where's my rounded corners and shadows? Fonts are another issue for me. I have to convert to EOT fonts just for IE while everyone else can handle OTF and others. In the article they dismiss compliance here too.
Someone more savvy than I (or less lazy) should write up a list of elements, selectors, and other features that are implemented in Gecko, Webkit, and Presto, but not IE and say, "Here's what developers want. Give us that or keep your browser."