- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Feb 2025 20:47:52 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-color-hdr] Add permission policy (or other mechanism) to irreversibly limit EDR`. <details><summary>The full IRC log of that discussion</summary> <jcraig> scribe+ jcraig<br> <jcraig> rrsagent, make minutes<br> <RRSAgent> I have made the request to generate https://www.w3.org/2025/02/26-css-minutes.html jcraig<br> <jcraig> scribe+ weinig<br> <weinig> smfr, issues is ads in cross origin frames showing hdr<br> <weinig> ... one way to got is not allowing HDR cross origin<br> <weinig> ... or we could use the property<br> <jcraig> s/simon: /smfr: /g<br> <weinig> ... or do we want to add to the iframe attribute that grants permissions<br> <jcraig> s/smfr, /smfr: /<br> <weinig> ... Is the definition of the css property on an iframe even specified?<br> <weinig> ... does it apply to all the contents?<br> <weinig> astearns:, do we have any cases where things don't propagate down into an iframe?<br> <weinig> smfr:, I think HDR is a little special, and we should we say something<br> <weinig> ChrisL:, this is a about stoping ads doing bad things<br> <weinig> smfr:, yes, but it is also about explicitly letting some cross origin iframes<br> <pal> q+<br> <weinig> ... this is partially a HTML issue, since the attribute would be in HTML<br> <weinig> astearns: the permission policy would be an attribute?<br> <jcraig> rrsagent, make minutes<br> <weinig> smfr: yes<br> <RRSAgent> I have made the request to generate https://www.w3.org/2025/02/26-css-minutes.html jcraig<br> <weinig> ChrisL: is this being discussed in HTML?<br> <weinig> smfr: I don't think so<br> <astearns> ack pal<br> <weinig> pal: this is complex, but someone who made an HDR video would be upset if they got squashed when embedded<br> <weinig> smfr: yeah, we currently always allow HDR on video<br> <weinig> ... so we may want to allow it to always work cross origin<br> <weinig> pal: codepen is an extreme example, because it wants the iframe to be perfect<br> <weinig> ... would be good to hear from website authors<br> <weinig> ... the default of showing in HDR is better than not, but can be jarring<br> <weinig> astearns: not sure who filed the issue, but the person who filed the issue seemed to want to be able to limit things<br> <weinig> smfr: actually, it was filed by a webkit engineer<br> <weinig> ... but others have mentioned a concern of ads<br> <weinig> pal: isn't the only thing you would ever want to do is make it all sdr?<br> <weinig> smfr: not sure, might have HDR but not want flashy ads to be HDR<br> <weinig> pal: I think the website should probably have control<br> <weinig> smfr: I think both the website author and user<br> <weinig> ... defaults we choose are important<br> <weinig> astearns: and giving authors the tools<br> <weinig> ... no way to currently allow a hosting page to say it only wants sdr<br> <weinig> smfr: this is a sleeping problem, since we only just started shipping HDR now<br> <weinig> weinig: I am not sure the issue of an embedded YouTube not being HDR is that big a deal<br> <weinig> ... you can always put a tinted div over a video<br> <weinig> ... letting the hosting site make things SDR seems fine<br> <weinig> jcraig: we had a similar issue internally with a feature that dims things automatically when things are flashy, and there was a question of whether it was ok to change the artists intent<br> <weinig> ... but ultimately, allowing the user to have the control was the way to go<br> <weinig> pal: movies are mastered under the idea they will be the only thing displayed<br> <weinig> ChrisL: yeah, but we can't do that on the web, we have to allow mixed content<br> <weinig> pal: yeah, when a movie is watched on the web, it is already compromised<br> <weinig> ... image gallery much more complicated<br> <weinig> astearns: ok, good talk, lets take this back to the issue<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11704#issuecomment-2686157917 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 February 2025 20:47:53 UTC