←back to thread

HDR‑Infused Emoji

(sharpletters.net)
274 points tabletcorry | 1 comments | | HN request time: 0.001s | source
Show context
jchw ◴[] No.43718242[source]
Looks like this works on Chrome for Android, but Firefox doesn't seem to support HDR at all.

https://bugzil.la/hdr

Maybe some day.

replies(3): >>43718264 #>>43719205 #>>43719259 #
lxgr ◴[] No.43718264[source]
Neither does Safari on macOS – which honestly seems like the correct behavior, given that this will inevitably be used by websites in user-hostile ways.
replies(1): >>43718319 #
lights0123 ◴[] No.43718319[source]
Safari only shows HDR in videos, not photos. It's possible to just show a single-frame video though.
replies(1): >>43718360 #
lxgr ◴[] No.43718360[source]
And I could see Safari changing its behavior to only allow HDR for actually playing videos (or even playing videos with actually varying content, if websites start playing clever games with one second loops of still images), or maybe only after confirming an "I am wearing sunglasses right now" prompt.
replies(2): >>43718447 #>>43718995 #
zamadatix ◴[] No.43718995[source]
If it were to become a real problem I'd sooner see Apple, of all vendors, leave it as one of the many settings flags in Safari than intentionally avoid or remove support for wide range media in their app.

Related: there is also a CSS property coming which allows sites to control which page content should be clamped to standard range or not. Worst case you can just add an * !important override in your Safari->Preferences->Advanced->Style Sheet if nobody else considers it problematic but you still wanted to clamp things (in Safari, otherwise you can just disable HDR).

replies(2): >>43719071 #>>43719695 #
tshaddox ◴[] No.43719695{3}[source]
Why would we expect this to become more of a problem than, say, websites playing audio quietly to encourage you to turn your volume up, than playing extremely loud audio?
replies(1): >>43719798 #
zamadatix ◴[] No.43719798{4}[source]
Websites can't autoplay audio anymore (which is actually really annoying in a few use cases) precisely because of abuse.

I don't think it'll be problematic though because a site can already choose to show you images a lot more bothersome than a bright light (I say this as I type on a 1600 nit HDR monitor) already and that's not a particularly common problem to worry about either. Same for videos, which already HDR support in browsers.

replies(1): >>43719894 #
tshaddox ◴[] No.43719894{5}[source]
> Websites can't autoplay audio anymore (which is actually really annoying in a few use cases) precisely because of abuse.

But this is hardly true. There are some complicated heuristics (like Chrome's "Media Engagement Index") but many websites can and do autoplay video and audio. And browser policies are even more relaxed for playing audio on user events (like clicking).

replies(1): >>43720468 #
1. zamadatix ◴[] No.43720468{6}[source]
MEI (and the like) is what I'm referring to, though perhaps we look at this from different angles. Sites can still mark audio should autoplay but it's now up to the browser to decide if it actually does it (because shitty sites would abuse that).