Firefox doesn’t implement the AudioData API, which is probably necessary for the waveform viewer and cropping tool Discord presents in the soundboard management UI.
Not everything is about Chrome DRM yall.
Edited to add screenshot of spoofing user-agent on Firefox and getting an error:
Yet another experimental API only supported by Chrome. Chrome has always been like this, implementing experimental API that hasn’t been finalized yet. You might say they’re innovating to support new technologies, but actually it’s more like they’re doing whatever they pleased, as demonstrated by their removal of jpeg xl support despite web communities plea not to do so (a new more efficient image compression, but not made by Google so screw it), pushing manifest V3 and ad topics, and recent push for web environment integrity API.
Not sure if these built in decoders are supported though. Seems a bit dangerous to expose native codecs directly from the web to be honest, since you’ll end up with wildly varying support across browsers.
I remember ages ago websites were all focused on “works best on Internet Explorer” or “please use Netscape for the best experience”
We managed a good solid decade after that where browsers all somewhat caught up to each other and now we’re going back that way again, with each website just YOLO implementing APIs that aren’t fully supported (with no polyfils or fallbacks)
When you did that back in IE7/8/9, you missed out on rounded corners or drop shadows, now whole parts of apps won’t work unless you’re on chrome 🤯
This is an experimental API that hasn’t been finalized yet. Firefox devs has limited engineering resource and simply can’t keep up with Chrome’s push to implement experimental/proposal API. Safari also hasn’t implemented this yet because they also usually wait until the API finalized, which can take quite a while.
Firefox doesn’t implement the AudioData API, which is probably necessary for the waveform viewer and cropping tool Discord presents in the soundboard management UI.
Not everything is about Chrome DRM yall.
Edited to add screenshot of spoofing user-agent on Firefox and getting an error:
Yet another experimental API only supported by Chrome. Chrome has always been like this, implementing experimental API that hasn’t been finalized yet. You might say they’re innovating to support new technologies, but actually it’s more like they’re doing whatever they pleased, as demonstrated by their removal of jpeg xl support despite web communities plea not to do so (a new more efficient image compression, but not made by Google so screw it), pushing manifest V3 and ad topics, and recent push for web environment integrity API.
EEE yall
How can they not support jpg xl? It’s such a huge thing
Firefox and Safari is also implementing experimental features often.
I think Moz helped write and supports this. I even think it’s (partially enabled in nightly?)
Not sure if these built in decoders are supported though. Seems a bit dangerous to expose native codecs directly from the web to be honest, since you’ll end up with wildly varying support across browsers.
I remember ages ago websites were all focused on “works best on Internet Explorer” or “please use Netscape for the best experience”
We managed a good solid decade after that where browsers all somewhat caught up to each other and now we’re going back that way again, with each website just YOLO implementing APIs that aren’t fully supported (with no polyfils or fallbacks)
When you did that back in IE7/8/9, you missed out on rounded corners or drop shadows, now whole parts of apps won’t work unless you’re on chrome 🤯
Any reason FF hasn’t implemented this?
This is an experimental API that hasn’t been finalized yet. Firefox devs has limited engineering resource and simply can’t keep up with Chrome’s push to implement experimental/proposal API. Safari also hasn’t implemented this yet because they also usually wait until the API finalized, which can take quite a while.
dont show firefox users any modern web feature
Hope you’ll continue to lick the Google even after Chrome implements DRM.
This isn’t a chrome is bad issue, this is a discord is bad issue. They shouldn’t be relying on an experimental feature.
im a firefox user
It appears the Reddit users that don’t read further than the title have arrived on Lemmy.
Shocking news: people are people everywhere, not just on ‘rival’ platforms.
Care to elaborate? I can’t make sense of your response
Yeah unfortunately it looks like they are here too, oh well at least it’s money out of spez’s hands