- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Mar 2022 17:26:14 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Making system colors fully resolve`. <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: Making system colors fully resolve<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/6773<br> <chris> https://github.com/w3c/csswg-drafts/issues/6773#issuecomment-1062008116<br> <fantasai> alisonmaher: Proposal is for both issue 3747 and 4915, which resolved to make system colors resolve to themselves and resolve at used value time<br> <fantasai> alisonmaher: Proposal is to resolve the colors, but flag them as being system colors, so that we don't force them when they're used in forced colors mode<br> <fantasai> alisonmaher: This would also allow to revert 6310, which added a special value for SVGs<br> <fantasai> alisonmaher: I'm not sure if there are specific color scheme resolutions that need to be checked<br> <fantasai> emilio: I need to check wrt retain that they were system colors bit, but the rest seems fine<br> <fantasai> chris: I asked whether you need to ask which system color, and they said not, it's just a single bit so that you know not to force the color<br> <fantasai> emilio: Ah, ok, that makes sense<br> <astearns> ack fantasai<br> <dholbert> scribenick: dholbert<br> <dholbert> fantasai: there was a comment a while back which is why we went in this direction...<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/4915#issuecomment-707969753<br> <dholbert> fantasai: this comment... I wonder if we're handling that somehow or if we have a problem<br> <fantasai> alisonmaher: I think we wouldn't be handle that case, we'd be inheriting the forced colors rather than author-specified values<br> <dholbert> scribenick: fantasai<br> <fantasai> alisonmaher: we originally shipped in Edge with forcing colors at computed value time, but ended up switching to used value time<br> <fantasai> alisonmaher: and we only got the opposite problem in SVG, in terms of bug<br> <fantasai> alisonmaher: I think it could be a good change, but maybe some cases where authors don't expect the behavior<br> <fantasai> TabAtkins: We solve either this one or the other one where an author-specified color naturally inherits into something with a forced background<br> <emilio> q+<br> <fantasai> TabAtkins: so I think our reverting resolution solves the more important of the issues<br> <fantasai> chris: I agree<br> <astearns> ack emilio<br> <fantasai> emilio: I agree with what Tab just said<br> <fantasai> emilio: Also, at this point, what is the difference between forcing at used value time and computed value time<br> <fantasai> alisonmaher: Difference is if authors sets 'forced-color-adjust: none', if at used-value time<br> <fantasai> alisonmaher: inherits color as if never forced<br> <fantasai> alisonmaher: [gives example]<br> <fantasai> alisonmaher: then would inherit the color that the author expected, but if at computed value time it would inherit the forced color that author doesn't expect<br> <fantasai> emilio: I wonder which behavior is better, but understand the difference<br> <dholbert> fantasai: what are we currently proposing to do with regards to this case?<br> <dholbert> chris: what alisonmaher proposed on that last issue<br> <dholbert> fantasai: particular to emilio's question: are we computing and then inheriting, or vice versa?<br> <fantasai> alisonmaher: Currently we inherit and then force the colors, and proposal is to force at computed value time so that you would inherit the forced colors instead<br> <dholbert> alisonmaher: since it's at used-value time, we're inheriting and then forcing the colors [...]<br> <fantasai> astearns: Seems like several issues<br> <fantasai> astearns: 3847, proposal is to revert the resolution. What was it?<br> <fantasai> chris: I see a lot of ppl being in agreement and fantasai being confused<br> <fantasai> astearns: fantasai, you're concerned that this set of resolutions would result in page getting a mix of forced colors and author colors that will result in bad color design<br> <fantasai> fantasai: yes<br> <fantasai> astearns: Should we explore that bad color design problem before making this set of resolutions, or should we make the resolutions and see how applying the resolutions turns out<br> <fantasai> chris: I suggest we try out and see if there's an issue<br> <fantasai> chris: I think it's the right way forward<br> <fantasai> chris: as Tab said, it solves the more important problem<br> <emilio> I agree<br> <dholbert> fantasai: not sure, I'm not really up to date with what's going on, and there's a lot going on in this issue<br> <dholbert> fantasai: how about we take them as tentative resolutions for 24 hours, and TabAtkins will explain them to me :)<br> <dholbert> astearns: how about we postpone making the resolutions until next week<br> <dholbert> fantasai: sounds good, but let's outline what we're resolving<br> <dholbert> astearns: That's alisonmaher 's comment. she outlines a 5-step process<br> <dholbert> astearns: take a look at her comment this week, and then next week we can resolve on all 5 items<br> <dholbert> astearns: any concerns about waiting another week?<br> <dholbert> chris: I'd prefer to get spec text drafted, but we can wait another week. I can still hash out some proposed spec text.<br> <dholbert> astearns: proposed text would probably make it easier to review in the meantime<br> <dholbert> astearns: emilio, please look at the proposed resolutions too<br> <dholbert> emilio: sounds good<br> <dholbert> astearns: everyone else who's concerned/interested, please also look, and we'll come back to this next week and resolve<br> <dholbert> astearns: thanks alisonmaher for the proposal<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-1063174175 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 March 2022 17:26:16 UTC