I have read almost all what was written/published at first glance about IE7, in english, french and even swedish. It just proves once again that people should think seven times before blogging bullshits. The I-ll-be-the-first-one-to-blog-about-it race is dangerous. I've also carefully read the list of improvements provided by Chris Wilson. The whole thing deserves a few very simple comments here:
- Extended CSS support in IE7, even if many people expected better than what's listed, is excellent news.
- IE7 adds support for the child selector. Wow. Fi-nal-ly! The '>' one. The FOAICB (father-of-all-ie-css-bugs; the mother being the box model). I heard a few years ago a Microsoft "representative" tell me and three others with me that adding support for '>' was not simple because of the original design of the layout engine... I guess they just missed a byte in their representation of a chain of selectors to code the combinator. Since the '+' combinator is also supported now, I guess somebody finally found enough time to add that byte, the event-based reentry and the stuff around. This raises a few questions:
- So it was not so hard/impossible to fix, right? Seriously, between gentlemen, is there a single good reason why we don't have at least '>' implemented in IE since 1998?...
- Is support for '+' and attribute selectors fully dynamic, as I hope it is?
- What's going to happen to the tons of web pages using hacks to "filter" IE6 based on the lack of support for combinators or rules or whatever? Since IE6 is not going to die any time soon (remember there are ol'Windows users?), we're going to end up with rendering conflicts between IE6 and IE7... Probably unacceptable from a customer's perspective.
- Could Microsoft (hear Chris Wilson) publish a Selectors Profile instead of just saying "CSS 2.1 Selector support (child, adjacent, attribute, first-child etc.)"? That would help a lot.
- Any plans to improve the CSS Object Model?
- Adding support for CSS3's "::" is important and should be done immediately, since it's quite simple to implement.
- I definitely agree with Chris about the Acid2 test. Some bits of it are just here to show a great respect of standards but do not necessarily improve drastically web authors' and visitors' experience. Remember the target of a browser is you, me, the girl next door, your mum, and even your salesperson (well, maybe not your salesperson, too dumb after all); the target of new language features in that browser is the Web author, and that's an entirely different beast...