Not that I recommend doing so, but in many cases you don't have a choice. Or you started working on a project that originally needed to, and maintaining consistent style might lead you to use jQuery everywhere.
Of course. My main point wasn't the use of querySelector per se, but the ability to access the exact DOM element(s) you need without crazy querying or traversal.
While the DOM API isn't perfect by any means, and jQuery fills that gap really well, there are still times where the OOP nature of the DOM gets you exactly what you want with minimal faff.
The other problem is the relative obscurity of it thanks to jQuery and crowd-sourced DOM documentation (via MDN).
yeah, jQuery certainly eclipses everything else. Though I don't know what you mean by obscurity + MDN... it does seem weirdly anaemic for such a big / complex / important piece of the API, but I don't know if I'd call MDN obscure. Or, I hope it isn't, I find it wildly useful.
Comments
Unless you want to support IE7, that is. http://caniuse.com/#search=queryselector
Not that I recommend doing so, but in many cases you don't have a choice. Or you started working on a project that originally needed to, and maintaining consistent style might lead you to use jQuery everywhere.
Of course. My main point wasn't the use of querySelector per se, but the ability to access the exact DOM element(s) you need without crazy querying or traversal.
While the DOM API isn't perfect by any means, and jQuery fills that gap really well, there are still times where the OOP nature of the DOM gets you exactly what you want with minimal faff.
The other problem is the relative obscurity of it thanks to jQuery and crowd-sourced DOM documentation (via MDN).
yeah, jQuery certainly eclipses everything else. Though I don't know what you mean by obscurity + MDN... it does seem weirdly anaemic for such a big / complex / important piece of the API, but I don't know if I'd call MDN obscure. Or, I hope it isn't, I find it wildly useful.