- From: Anne van Kesteren via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Feb 2024 18:03:56 +0000
- To: public-css-archive@w3.org
annevk has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-ui] Clarify scope of implementation-defined behavior for native appearance (and primitive appearance) == While discussing https://github.com/web-platform-tests/wpt/pull/44138 via email with @zcorpan he raised this point: > I had a different understanding of the "may disregard some CSS properties" language in the spec. Changing computed styles of other properties based on native/primitive appearance seems like a fundamental change to how the CSS cascade normally works that I think it should be explicitly defined. As an example, for the switch control the native appearance uses `display:inline-grid` (though `display:block` and the like will compute to `display:grid`). But when you change to the primitive appearance it'll always have `display:initial`. (When this was discussed during a WHATNOT call that was what the people attending preferred.) Being able to change properties (as well as some other things) in this way will also be essential for the inevitable `appearance:base-bikeshed`. cc @nt1m Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9919 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 February 2024 18:04:00 UTC