- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Nov 2021 17:52:46 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `@color-profile to L5`, and agreed to the following: * `RESOLVED: Move @color-profile and device-cmyk() to L5` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: @color-profile to L5<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/6765<br> <fantasai> lea: Custom color spaces have not gotten same implementer interest of other features in L4<br> <fantasai> lea: and complicate a lot of discussoins due to custom color spaces<br> <fantasai> lea: also had some ideas that depend on L5 features<br> <TabAtkins> q+<br> <fantasai> lea: so suggestion is to defer to L5<br> <fantasai> lea: but Tab raised that device-cmyl() depends on it<br> <fantasai> lea: which is implemented only in print impls<br> <fantasai> lea: Suggest is to also defer device-cmyk()<br> <chris_> q+<br> <fantasai> TabAtkins: I agree with this, and there's a lot of interesting things to work on here<br> <Rossen_> ack TabAtkins<br> <fantasai> TabAtkins: that could use time to bake without holding up L4<br> <fantasai> chris_: I also agree<br> <Rossen_> ack chris_<br> <fantasai> chris_: also have some feedback, have a descriptor called 'components' that doesn't appear to do anything because what it affects is in L5, so another reason to move<br> <fantasai> Rossen_: so proposed to move @color-profile and device-cmyk() to L5<br> <fantasai> RESOLVED: Move @color-profile and device-cmyk() to L5<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6765#issuecomment-965592183 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 November 2021 17:52:49 UTC