| Using "CSS selectors" to traverse a tree of nodes is utterly stupid. Clearly your opinions differ from the majority of the web community. Why do you think we now have document.querySelectorAll? Have a look at the mdn article: https://developer.mozilla.org/en/DOM/Document.querySelectorA... example given on that page: var matches = document.querySelectorAll("div.note, div.alert"); also : http://www.w3.org/TR/selectors-api/ Makes perfect sense. That's what recursion/tree traversal algorithms are for No. That's what highly optimized browser internals are for. I test all the way back to IE 5.5 Why? ie5.5 is 12 years old. |
> Why do you think we now have document.querySelectorAll?
This is called "argumentum ad populum" (appeal to popularity). The advent of jQuery caused clueless "developers" (along with library authors) to beg for "native" selectors. QS(A) is the result. They were never needed in the first place.
> Why? ie5.5 is 12 years old.
Internet Explorer's Quirks Mode (which still exists in IE 9) is a simulation of IE 5. It's useful for testing against IE's old box model.