4 ms·
You are misinformed. Firefox had their own implementations of WebUSB and WebBluetooth years and years ago -- they were necessary for FirefoxOS. Deprecating an
by stonogo 4y ago
You are misinformed. Firefox had their own implementations of WebUSB and WebBluetooth years and years ago -- they were necessary for FirefoxOS. Deprecating and removing them was a conscious decision because the privacy risks were deemed too great. This is also the case for Manifest v3; Mozilla is trying to determine the 'safe' (i.e. user-friendly) characteristics to implement and ways to mitigate the rest. Some parts of v3 directly conflict with Firefox architecture. As an example, v3 requires service workers, while Firefox permits entirely disabling them.
The overarching theme of your writing on this topic is that Chrome can just spit out Web 'features' at random and unless Firefox implements all of them immediately it is dying. I hope you can try to understand that not only is this not an accurate assessment, but maybe also that Firefox has value beyond being a copy of Chrome.
- fabrice_d 4y agoThe security model used in Firefox OS to gate access to these APIs was very different. We never exposed these web bluetooth to the web at large, only to signed apps. Mozilla needs to step up and find ways to expose such APIs though, because they are useful. Just saying "no" without proposing a solution is a sure way to lose. There's a bit of hope recently with the implementation of WebMIDI in Gecko.