Re: [csswg-drafts] [css-ui] `revert-layer` rolling back to author origin should disable native appearance (#7239)

The CSS Working Group just discussed `[css-ui] revert-layer rolling back to author origin should disable native appearance`, and agreed to the following:

* `RESOLVED: For properties that disable native appearance, do all the reverting, take into account the origin of the final cascaded value`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> topic: [css-ui] revert-layer rolling back to author origin should disable native appearance<br>
&lt;emilio> github: https://github.com/w3c/csswg-drafts/issues/7239<br>
&lt;emilio> oriol: there are some properties than when set on autor/animation origin disable native appearance unless `revert` / `revert-layer` is specified<br>
&lt;emilio> ... for revert it makes sense<br>
&lt;emilio> ... since it always reverts to user/ua origin<br>
&lt;emilio> ... but revert-layer can revert to author origin<br>
&lt;florian> q+<br>
&lt;emilio> ... and in this case it should disable native appearance<br>
&lt;emilio> ... all implementations already behave like this<br>
&lt;emilio> ... so proposal is to align with implementations<br>
&lt;astearns> ack florian<br>
&lt;emilio> florian: I think it's over-correction, original spec forgot revert-layer but forgot taking this into account<br>
&lt;emilio> ... if you have multiple revert-layers, how does this behave? Is it feasible to check all of them?<br>
&lt;emilio> oriol: I didn't test this more complex case<br>
&lt;emilio> florian: could we spec that however many layers you revert you account for that, and revisit if it's problematic?<br>
&lt;emilio> q+<br>
&lt;astearns> ack emilio<br>
&lt;fantasai> emilio: I just wanted to say, you do need to revert all the layers<br>
&lt;fantasai> emilio: you need to get to the original value<br>
&lt;fantasai> emilio: so I think it makes sense to spec this, it's the sensible thing to do<br>
&lt;emilio> so, +1<br>
&lt;emilio> RESOLVED: For properties that disable native appearance, do all the reverting, take into account the origin of the final cascaded value<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7239#issuecomment-1183460954 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 13 July 2022 16:53:42 UTC