News for hackers. Stuff that matters.

A comment on WhatWG: Proposal – Update XPath to at least v2.0. Parent comment

Re:WhatWG: Proposal – Update XPath to at least v2.0 by dmitriid on Tuesday October 13, 2020 @01:14PM (#24767564)
The web is not just WHATWG. Chrome rams multiple standards through several standards bodies. Scroll down in Mozilla's standards positions [1]. Then search for the harmful standards in Chrome features: [2]

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.

[1] https://mozilla.github.io/standards-positions/

[2] https://chromestatus.com/features

[ Parent | on HN ]
Re:WhatWG: Proposal – Update XPath to at least v2.0 by sergeykish on Tuesday October 13, 2020 @01:50PM (#24767926)
The original issue is WHATWG, conversation should stick to WHATWG first:

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...

[2] https://news.ycombinator.com/item?id=24766845

[ Parent | on HN ]