7 ms·
A lot of these don't work in any browser other than Chrome. Demos that work in Firefox: - Fullscreen - Image capture - Resize observer - Broadcast Channel
by jeroenhd 6y ago
A lot of these don't work in any browser other than Chrome. Demos that work in Firefox:
- Fullscreen
- Image capture
- Resize observer
- Broadcast Channel
Demos that don't:
- Clipboard API (not supported)
- Battery API (not supported)
- Performance information (says it's supported, but shows an empty page)
- Vibration API (supported by the browser, but doesn't actually vibrate because malvertisers abuse the API in their antivirus scams)
- Bluetooth API (not supported)
The fullscreen, image capture and broadcast channel APIs are nice I suppose, but the rest should probably be considered "Chrome APIs" rather than "web APIs".
Edit: even in Chrome on Android, the battery API is reporting fake information and the vibration demo doesn't work. That's the problem with experimental web APIs, you can't rely on them at all.
- dastx 6y agoCould it be that you've got antitracking mechanisms enabled? Noscript, enhanced tracking protection or something else? They could very well prevent Firefox from accessing said APIs Edit: never mind, I just checked some, and they're all not supported according to caniuse. Interesting to see Firefox used to support battery api, but was removed for public consumption as of 52 due to privacy concerns.
- Phrodo_00 6y agoYeah, I'm not sure Firefox would choose to implement some of the APIs in the not implemented list. The chance they can be used for fingerprinting is pretty high.
- onion2k 6y ago...the rest should probably be considered "Chrome APIs" rather than "web APIs". That's just plain wrong. They're web APIs that are maintained by the W3C (in various states) that Firefox doesn't support yet. That doesn't make them "Chrome APIs" just as a W3C spec that only Firefox supports isn't a "Firefox API". Clipboard API: https://w3c.github.io/clipboard-apis/ https://w3c.github.io/clipboard-apis/ Battery API: https://w3c.github.io/battery/ https://w3c.github.io/battery/ Performance: https://www.w3.org/TR/resource-timing/ https://www.w3.org/TR/resource-timing/ Bluetooth API: https://webbluetoothcg.github.io/web-bluetooth/ https://webbluetoothcg.github.io/web-bluetooth/ The fact there isn't good cross-browser support is a reason to check whether or not a user's browser has support and use progressive enhancement to only show the feature to users who can benefit from it. It isn't a reason to avoid using the API unless you want to stick to the lowest common denominator for your users. In my case that would mean serving Chrome and Firefox users content that's developed for IE10. That would suck for people who are able to update their browser, so I prefer to put the effort in to adding features progressively.
- userbinator 6y agoGoogle essentially controls the W3C now.
- tasogare 6y agoThey also develop the browser that has the sheer majority of users and fund almost exclusively the only real technical competitor. This is really worrying.
- Spivak 6y agoSafari? And just because MS is rebasing on Chromium doesn’t mean they still don’t have a lot of technical might to throw at Edgeium.
- josteink 6y ago> That's just plain wrong. In theory yes, in practice no. If code doesn't run in 1 of 2 the browser-engines we currently have, I would consider that a major short-coming preventing me from using it in production.
- DarthGhandi 6y agoHow many of your production end users are using firefox? Low single digits?
- josteink 6y agoI am using Firefox, and I find that attitude among developers infuriating. If not enough users are using a platform, let's actively sabotage for that platform by making it less viable, further justifying your own laziness? Is that it? As someone who has gone from Amiga, to Mac, to Windows PCs, to FreeBSD and now Linux (not to mention the smart-phone story!), I take pride in my work being portable and cross-platform friendly. I have absolutely no desire to go back to the mono-culture days of MSIE. If you put it on the web, it should work everywhere, otherwise you're just being lazy and/or incompetent.
- nicoburns 6y agoFirefox supports at least some of the clipboard APIs. They'll likely support a few more in future (like the async variants). But they tend to implement them a little slower and leave out a few bits due to privacy concerns.
- bartread 6y agoAlso, full screen doesn't work in iOS Safari. It was supported but that support was removed several years ago (I want to say 2014, but may be a little off).
- madeofpalk 6y agoOff the top of my head, i believe it only works on iPad Safari?
- chris_st 6y agoThe Clipboard API demo works fine in Safari.
- Aardwolf 6y agoThe battery API has been in the news before: https://www.theguardian.com/technology/2016/nov/01/firefox-disable-battery-status-api-tracking https://www.theguardian.com/technology/2016/nov/01/firefox-d...
- toomanybeersies 6y agoFirefox supports the performance API for timing, but not for memory.
- wayneftw 6y agoGood for Chrome. That's why I use it and that's why I build apps that have features which are exclusive to Chrome and Microsoft Edge. All other browsers are second-class citizens IMO. If they don't want to add features that I want, then fuck 'em. I'll keep telling all my customers that if they don't use Chrome or Edge, then they're missing out.