W3C home > Mailing lists > Public > public-css-archive@w3.org > March 2020

Re: [csswg-drafts] [css-color-adjust-1] User origin !important vs. forced colors mode (#4020)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 18 Mar 2020 16:36:17 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-600735820-1584549375-sysbot+gh@w3.org>
The CSS Working Group just discussed `[css-color-adjust-1] User origin !important vs. forced colors mode`, and agreed to the following:

* `RESOLVED: Option 3- Rewrite all author rules for affected properties to specify 'revert' instead`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-color-adjust-1] User origin !important vs. forced colors mode<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4020<br>
&lt;dael> fantasai: The spec says we add revert !important at user level to wipe out author level. Also reverts entire user level of cascade<br>
&lt;dael> fantasai: I think intent was leave user styles.<br>
&lt;dael> fantasai: If we want to do that correctly need origin between user and author. Sort of have this which is non-css presentation layer. It's beginning of author and has no spec<br>
&lt;dbaron> could these rules just be in the author level (at the top)?<br>
&lt;dael> fantasai: We could define there's a new UA control layer called presentation-hints and importance is between user and author and then it works as intended. Or we can do something else. Currently spec doesn't work as intended<br>
&lt;dael> AmeliaBR: If we can explain behavior using source order; say this is inserted at origin before any other rules at origin; I think that's easier than new cascade origin. If that doesn't work then define it explicitly<br>
&lt;dael> fantasai: emilio says they treat all author level as revert so we can spec that way.<br>
&lt;dael> astearns: Is this something where we have more tools to solve when we get to custom origins prop?<br>
&lt;dael> fantasai: No b/c need to revert...revert in author needs to revert non-css presentaiton hints. So we can create a new origin or do what emilio says FF is doing<br>
&lt;dael> astearns: Set of properties?<br>
&lt;dael> fantasai: [missed]<br>
&lt;dael> emilio: I don't understand why revert !important wouldn't work at end of author. Might be easier to spec that way. In practice I think the obserables are same as FF.<br>
&lt;dael> fantasai: I'm happy to put in FF behavior<br>
&lt;dael> astearns: Any concerns with specify FF behavior?<br>
&lt;dael> astearns: Reading emilio comment: Treat author level declarations with a set of properties as revert<br>
&lt;dael> fantasai: 3 solutions. Creat new origin<br>
&lt;fantasai> 1. Create new origin between author / user origins<br>
&lt;fantasai> 2. Insert 'revert !important' rules in author orgin with highest possible specificity<br>
&lt;dael> fantasai: I think 3 is what emilio is saying FF does<br>
&lt;fantasai> 3. Rewrite all author rules for affected properties to specify 'revert' instead<br>
&lt;dael> fantasai: All of those would work. I don't have an opinion between.<br>
&lt;dael> astearns: I think 3 is easiest to explain to authors. Just my personal opinion<br>
&lt;dael> fantasai: That's a vote for easy to explain and a vote from FF it's easy to impl<br>
&lt;dael> Rossen_: I think #3 makes sense<br>
&lt;dael> astearns: AmeliaBR okay to you?<br>
&lt;dael> AmeliaBR: Yeah. So long as clearly defined.<br>
&lt;dael> astearns: Prop: Option 3- Rewrite all author rules for affected properties to specify 'revert' instead<br>
&lt;dael> astearns: Objections?<br>
&lt;dael> RESOLVED: Option 3- Rewrite all author rules for affected properties to specify 'revert' instead<br>
&lt;dael> astearns: Thanks emilio for adding FF behavior<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4020#issuecomment-600735820 using your GitHub account
Received on Wednesday, 18 March 2020 16:36:19 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:02 UTC