- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Feb 2025 20:32:12 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-color-hdr] How should multiple layered elements with different `dynamic-range-limit` values behave?``, and agreed to the following: * `RESOLVED: modify spec text as discussed, to try and flesh out if there are blocking compositor issues in implementations; possibly add an appendix of test cases and blocking issues with platform limitations` <details><summary>The full IRC log of that discussion</summary> <jcraig> weinig: for multiple layered elements, need more added to clarifying the model underlying what this property actually does<br> <jcraig> uses tone map example<br> <jcraig> s/map example/map compositing example to explain compositor controlling whether this is additional headroom/<br> <jcraig> ChrisL: we have a brief section on compositing... would be good to get better text<br> <jcraig> weinig: understanding what implementors would like to apply here would be useful<br> <jcraig> and the constraints of existing compositors<br> <jcraig> Said: the dynamic range limit is cascading, correct?<br> <jcraig> weinig: inherited but overridden by an explicit defining on higher specificity<br> <jcraig> simon: yes, agreed at F2F that these are not multipliers<br> <jcraig> ChrisL: should be documented, possibly in an appendix...<br> <jcraig> easy to write something that looks great from a color theory perspective but may not be implementable<br> <jcraig> PROPOSAL: modify spec text as discussed, to try and flesh out if there are blocking compositor issues in implementations; possibly add an appendix of test cases and blocking issues<br> <jcraig> weinig: WPT is lacking here because the color space can be modified<br> <jcraig> ChrisL: and WPT is limited to sRGB<br> <jcraig> s/PROPOSAL: modify spec text as discussed, to try and flesh out if there are blocking compositor issues in implementations; possibly add an appendix of test cases and blocking issues/PROPOSAL: modify spec text as discussed, to try and flesh out if there are blocking compositor issues in implementations; possibly add an appendix of test cases and blocking issues with platform limitations/<br> <jcraig> RESOLVED: modify spec text as discussed, to try and flesh out if there are blocking compositor issues in implementations; possibly add an appendix of test cases and blocking issues with platform limitations<br> <jcraig> weinig: I will take that 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/11307#issuecomment-2686126998 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:32:13 UTC