-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add querySelector test, addresses #1194 #1195
Conversation
Thanks Andrew. We have a module for Dumb questions:
|
Yes. I know of now implementations that don't implement both, but happy to AND the two checks.
I found https://github.com/termi/CSS_selector_engine. To be honest I'm more concerned about declaring requirements in terms of Modernizr tests than providing means of satisfying them, but from a quick search this seems reasonable.
A quick search suggests http://www.w3.org/TR/selectors-api/#queryselectorall, but I'm not sure if that's the canonical spec. |
I've addressed the docs and additional property test. Haven't added the polyfill - let me know if you need that and if @termi's one is the right one to use. |
Me too, generally – I’d probably use jQuery instead of polyfilling |
Hi all! I'm not working on my querySelector Polyfill throughout the year, but I can go back to work on it. Right now I need a feedback: that is good and that need to be improved. |
Are you happy to accept this now, @stucox? |
👍 Cheers! |
Add querySelector test, addresses #1194
Add querySelector test, addresses Modernizr#1194
Wasn't sure whether document should be an injected dependency, but the convention seems to be to assume it's a global, so have followed that.