I've just noticed that IE7 also fails to add quote marks around content contained in the q element.
How do Microsoft's development team fail to meet standards so badly?
Robin_reala
9:01 pm on Oct 22, 2006 (gmt 0)
By prioritising. From their point of view the easiest way to support the <q> element is to implement the ::before and ::after pseudoelements. This was pushed back in order to be able to concentrate on other things. Personally, I’d much happier that they decided to support min- and max-width (which almost didn’t make it in) over ::before and ::after.
UserFriendly
11:04 pm on Oct 22, 2006 (gmt 0)
Yeah, I have to say that I'm glad that min- and max- finally got added. But I'm not bashing MS for the sake of it. It just seems so poor that Internet Explorer has been lagging behind for years. It's not as if MS is a poor, penniless shareware company that can't muster the resources to improve their software.
I was really hoping that IE7 would mean the end of creating a new page, only to find it needed to be heavily modified to appease Internet Explorer. So I'm disappointed to see that we're not quite there yet.
Robin_reala
6:41 am on Oct 23, 2006 (gmt 0)
Yeah, I know. Fwiw I’m pretty sure that ::before and ::after will be added for the next version, and therefore the <q> element.
UserFriendly
1:06 pm on Oct 23, 2006 (gmt 0)
By "the next version" do you mean IE8? I think I might have died of frustration by then.
Robin_reala
1:09 pm on Oct 23, 2006 (gmt 0)
Microsoft works in mysterious ways :) There was a 12 month release cycle hinted at...
zachariah
7:26 pm on Nov 4, 2006 (gmt 0)
I think supporting the most basic web standard (HTML) is as important as security issues in IE.