9 ms·
Their official position cites security as the reason they haven't implemented it yet. https://mozilla.github.io/standards-positions/#web-bluetooth https://moz
by ff2400t 3y ago
Their official position cites security as the reason they haven't implemented it yet.
https://mozilla.github.io/standards-positions/#web-bluetooth https://mozilla.github.io/standards-positions/#web-bluetooth
- deleted 3y ago[deleted]
- JimDabell 3y agoThere’s a stack of Blink-only Google specifications that people are pushing as “standard” that are anything but. Both Apple and Mozilla reject them on privacy or security grounds, then get criticised as being “behind” (or in Apple’s case, “deliberately holding back the web”). No, a specification created and implemented unilaterally by Google is not a standard.
- charcircuit 3y agoMost standards start by being implemented by one browser. I would rather a standard exist based off a real implementation than one thrown out of an ivory tower.
- ff2400t 3y agoThe whole point of standards is that there should be multiple implementations that can support it. Now I do agree with your point on that standards should be based on feedback from implementations but as the above comment said, this is just google making adding features and making standard documents to shift blame on other browser for not implementing them.
- charcircuit 3y agoTo be fair where are the other browser's proposals for giving apps the capabilities they need? Browsers should be shamed for not making an effort to support common use cases that apps need.