@@ -34,7 +34,7 @@ Other fixes/standardized behaviors include:
***new** [DOM Listener: capture, passive, and once](https://www.webreflection.co.uk/blog/2016/04/17/new-dom4-standards)
* fully normalized `KeyboardEvent`, `MouseEvent` and the latest way to create `new Event('type')`
* [Elements as Array subclass](http://www.w3.org/TR/2015/WD-dom-20150428/#elements), so that `el.query` is the relative equivalent of `el.querySelector` and `el.queryAll` is the relative equivalent of `Array.prototype.slice.call(el.querySelectorAll(css))`. Relative means `node.query('body p')` won't return any `p` element contained in `node`, while old `querySelector` would.
- ***document.queryAll(css)** returns an Array so there's no need to use `Array.prototype.slice.call(document.querySelectorAll(str))` or `[...document.querySelectorAll(str)]` or `Array.from(document.querySelectorAll(css))`, just `queryAll` for a list or `query` to get one element. We can forget the `Selector` bit \o/
+ *[DROPPED PROPOSAL](http://stackoverflow.com/questions/23269785/whats-the-difference-between-queryall-and-queryselectorall/38245620#38245620) **document.queryAll(css)** returns an Array so there's no need to use `Array.prototype.slice.call(document.querySelectorAll(str))` or `[...document.querySelectorAll(str)]` or `Array.from(document.querySelectorAll(css))`, just `queryAll` for a list or `query` to get one element. We can forget the `Selector` bit \o/
* [classList](http://www.w3.org/TR/dom/#domtokenlist), with forced fixes for iOS 5.1 and Nokia ASHA Xpress Browser and early implementations
* [CustomEvent](http://www.w3.org/TR/dom/#customevent) constructor for all browsers down to IE8
* [Element#matches](https://dom.spec.whatwg.org/#dom-element-matches) utility to test elements against CSS selectors
WebReflection
committed
on GitHub
0 comments on commit
c39f3af