this post was submitted on 16 May 2024
69 points (96.0% liked)
Firefox
17902 readers
24 users here now
A place to discuss the news and latest developments on the open-source browser Firefox
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don’t think they thought this through.
Why not? They are one of the last browsers to add support, so I think they quite did?
One of the last browsers out of the two that exist (ignoring those that don't really develop any of those features themselves)?
What about Safari?
Safari is also just one of the forks of the KHTML/WebKit/Blink codebase Chrome is based on. Admittedly they probably implement some of the stuff they do implement themselves too because the common ancestor version is quite a long time ago now.
They don't incorporate chromium changes in safari, so it should be considered separate.
It’s a vendor specific feature, as opposed to something any graphics chip can use. It’s kinda like… endorsing a closed source driver feature.
Meh, with games we want them to work independent of which type of controller we use, but display each driver's specific button graphics as needed. I see no difference here. Do I want dynamic upscaling and auto-HDR for all graphics cards? Sure! Do I still want it optimized for each type of graphics card unless the hardware makers can - unlikely - present a unified API? Of course I do.