You'll see most of them already released publicly. And people like @spankalee will call you a hater when you start calling Google out. And then clueless web devs will complain how "Safari is holding the web back" even though Safari and Mozilla can barely hold back the floodgates of poorly specified standards that are being pushed through at neck-breaking speed.
https://wicg.github.io/webusb/
https://webbluetoothcg.github.io/web-bluetooth/
https://www.w3.org/2012/nfc/web-api/
https://www.w3.org/TR/html-imports/ # that one scrapped
That is not WHATWG.
WebReflection shows a great example of civilized discourse [1]. If excuse not to extend feature is low usage we'd better provide competing arguments how it is useful. If problem is usability we should address it first [2].
[1] https://github.com/whatwg/dom/issues/903#issuecomment-707828...
I like XML, XHTML, XPath, XSLT. But I don't understand your argument. Maybe it would look better with a list of harmful Chrome only APIs standardized by WHATWG. Even then it is not a reason to follow bad example.
[1] http://dom-report.herokuapp.com/