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.
The W3C encourages browsers to add experimental APIs so that developers can test them. Do you expect a brand new browser to be rolled out every time someone comes up with an idea?
The issue is with sites using a working draft in production. We also don’t know if that’s what’s happening or if that’s the API being used, though.The W3C encourages browsers to add experimental APIs so that developers can test them. Do you expect a brand new browser to be rolled out every time someone comes up with an idea?
The issue is with sites using a working draft in production. We also don’t know if that’s what’s happening or if that’s the API being used, though.
Edit: It is Discord using the AudioData API. Again, though, that’s on them. Experimental APIs aren’t supposed to be used in production since the standard can, and often does, change.
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 🤯
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
The W3C encourages browsers to add experimental APIs so that developers can test them. Do you expect a brand new browser to be rolled out every time someone comes up with an idea?
The issue is with sites using a working draft in production. We also don’t know if that’s what’s happening or if that’s the API being used, though.The W3C encourages browsers to add experimental APIs so that developers can test them. Do you expect a brand new browser to be rolled out every time someone comes up with an idea?
The issue is with sites using a working draft in production. We also don’t know if that’s what’s happening or if that’s the API being used, though.
Edit: It is Discord using the AudioData API. Again, though, that’s on them. Experimental APIs aren’t supposed to be used in production since the standard can, and often does, change.
How can they not support jpg xl? It’s such a huge thing
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.
Firefox and Safari is also implementing experimental features often.
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 🤯