552
"...is not supported in this browser", fuck you Discord
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Aug 2023
552 points (89.2% liked)
Technology
58133 readers
4512 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
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
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 🤯