- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Jul 2022 16:53:40 +0000
- To: public-css-archive@w3.org
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> <emilio> topic: [css-ui] revert-layer rolling back to author origin should disable native appearance<br> <emilio> github: https://github.com/w3c/csswg-drafts/issues/7239<br> <emilio> oriol: there are some properties than when set on autor/animation origin disable native appearance unless `revert` / `revert-layer` is specified<br> <emilio> ... for revert it makes sense<br> <emilio> ... since it always reverts to user/ua origin<br> <emilio> ... but revert-layer can revert to author origin<br> <florian> q+<br> <emilio> ... and in this case it should disable native appearance<br> <emilio> ... all implementations already behave like this<br> <emilio> ... so proposal is to align with implementations<br> <astearns> ack florian<br> <emilio> florian: I think it's over-correction, original spec forgot revert-layer but forgot taking this into account<br> <emilio> ... if you have multiple revert-layers, how does this behave? Is it feasible to check all of them?<br> <emilio> oriol: I didn't test this more complex case<br> <emilio> florian: could we spec that however many layers you revert you account for that, and revisit if it's problematic?<br> <emilio> q+<br> <astearns> ack emilio<br> <fantasai> emilio: I just wanted to say, you do need to revert all the layers<br> <fantasai> emilio: you need to get to the original value<br> <fantasai> emilio: so I think it makes sense to spec this, it's the sensible thing to do<br> <emilio> so, +1<br> <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