3 ms·
> You realise, right, that Firefox is also not keen on implementing this api? [1] And many others [2] Yeah, Mozilla used to be the beacon of Web standards, wha
by throw_m239339 5y ago
> You realise, right, that Firefox is also not keen on implementing this api? [1] And many others [2]
Yeah, Mozilla used to be the beacon of Web standards, what happened to them? They always find some silly justification to refuse implementing a spec, like WebSQL, half of the Web Component spec, and many many other things, what gives?
Chrome might be "bad" cause Monopoly, but Google is much much more pro-active in implementing useful standard proposals.
- dmitriid 5y ago> Mozilla used to be the beacon of Web standards, what happened to them They still are. Only now Google inundates everyone with Google-designed Chrome-internal "standards", and releases them against any objections. See WebHID as the best example of this: Issue https://github.com/mozilla/standards-positions/issues/459#issuecomment-753864467 https://github.com/mozilla/standards-positions/issues/459#is... and timeline https://news.ycombinator.com/item?id=27512354 https://news.ycombinator.com/item?id=27512354