- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Feb 2022 17:34:48 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-color] [css-color-adjust] Consider reversing the resolution of #3847`. <details><summary>The full IRC log of that discussion</summary> <emeyer> Topic: [css-color] [css-color-adjust] Consider reversing the resolution of #3847<br> <lea> I don't need to be here for that, dropping off<br> <emeyer> Github: https://github.com/w3c/csswg-drafts/issues/6773<br> <emeyer> emilio: I think this is the right thing to do, otherwise interpolation becomes very messy.<br> <emeyer> TabAtkins: After review, I agree with Emilio and it would be best to reverse the decision.<br> <Rossen_> q<br> <emeyer> …We should resolve that system colors should compute at computed style time.<br> <alisonmaher> q+<br> <emeyer> chris: So this is reversing for system colors but not currentColor.<br> <emeyer> alisonmaher: What will this mean for use value time?<br> <Rossen_> ack alisonmaher<br> <emeyer> emilio: The only reason I started looking into this is because of the preserve keyword. If you force colors at use value time, it’s bad.<br> <emeyer> Rossen: We have a resolution for forced colors that they resolve in used value time. That meant we could avoid the color mix function.<br> <emeyer> emilio: Where was it required? Just for backgrounds and alpha?<br> <emeyer> …Otherwise, system colors are preserved. Backgrounds are a special case.<br> <emeyer> …Gecko implements this with magic, not color mix. Could implement with color mix as well.<br> <emeyer> alisonmaher: This could re-raise an issue around forced-color-adjust.<br> <emeyer> emilio: I don’t see why that would be a problme.<br> <emeyer> s/problme/problem/<br> <Rossen_> ack fantasai<br> <emeyer> fantasai: I think one problem would be that with the default color on the canvas, if you change the color scheme at any point lower than root, it should have no effect.<br> <emeyer> TabAtkins: Because background colors aren’t inherited, if you change color scheme to the opposite, if the background is transpaarent, you end up with black on black or white on white.<br> <emeyer> …If you explicitly set colors with the scheme, you get what you expect. But it’s not reasonable to expect that flipping scheme will make things unreadable.<br> <fantasai> s/it should have/it would have/<br> <JakeA> is everyone just silent or have I dropped out?<br> <emeyer> (silence)<br> <Rossen_> q<br> <Rossen_> q<br> <emeyer> Rossen: Anyone who is still concerned about the effect of this change or the handling of forced-color-adjust, if this is something that doesn’t sound right yet, we can take another week to consider so we don’t end up flipping back and forth.<br> <emeyer> dlibby: I wouldn’t mind more time to think through, given Blink has shipped this behavior for a year or so.<br> <emeyer> TabAtkins: We did ship, but other things we’re doing don’t match the spec, so changing this wouldn’t have an enormous effect, I believe. There are still details to work out.<br> <fantasai> s/work out/work out with forced-colors mode, though, so happy to delay a week as well/<br> <emeyer> Rossen: Let’s give it a week. We’ll prioritize this next week.<br> <JakeA> https://github.com/w3c/csswg-drafts/pull/6533#issuecomment-1023455165<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6773#issuecomment-1041916451 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 February 2022 17:34:51 UTC