I think that in CSS 3, the new attribute selectors, nth-child variants and pseudo-classes such as :checked etc definitely can be useful, while not all the time.

With all respect to John, his post is interesting and definitely good information since I believe that those selectors are amongst the most common ones, but there a lot more web sites out there who use other selectors as well.

I think, just as it has been for other web browsers, if they get the general support into their CSS base then it will be a fairly easy feat to get it into querySelectorAll as well.

Also, see John Resig’s post about CSS3 selectors that people actually use, http://ejohn.org/blog/selectors-that-people-actually-use/ If you remove the ones that people don’t really use then there are not that many left for MS to add and they seemed to be willing to add parts of CSS3 as needed (they added box-sizing).

querySelector and querySelectorAll… nuf said

Well, not really. I was impressed at first, but from what I’ve seen, their support only covers up to CSS 2.1 and some CSS 3 features. Since WebKit, and any other web browser implementing this soon, will naturally support CSS 3 completely as well, this means yet another check and workaround, which in many cases will render querySelectorAll useless.

You state that Opera implements DOM storage. Could you point me to a resource which supports this? Same with Webkit. I know they have DB storage, but DOM storage?
http://bugs.webkit.org/show_bug.cgi?id=11245

Side note: Quite funny to see that MS picked up the name “DOM storage” from the Mozilla guys. Seems like HTML 5’s “Client-side session and persistent storage of name/value pairs” isn’t that catchy.

Thanks!

Thanks,
Jeff