- From: Anne van Kesteren via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Mar 2024 17:46:32 +0000
- To: public-css-archive@w3.org
annevk has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-ui] Styling of native appearance == HTML has a number of open issues around defining the native appearance of various widget types (as red boxes in the standard). However, it seems to me that HTML's role in this should be relatively small. For the majority of widgets we essentially need a box with an implementation-defined intrinsic width and height (not aspect ratio), to which a number of CSS properties apply and the remainder of CSS properties end up ignored. And as far as the native appearance goes I think generally any pseudo elements ought not to be applicable (this would automatically follow if they are defined as replaced elements as @emilio pointed out to me). --- At the bottom of https://drafts.csswg.org/css-ui/#appearance-switching there is a list of properties that ought to be applicable to widgets with a native appearance. This list seems incomplete. `writing-mode`, `transform`, `filter`, `transition`, `width`, `height`, and likely quite a few other properties need to work as well I think. I'm not entirely sure how we can classify CSS properties such that whenever a new property is added it is clear whether it needs to be honored for widgets with a native appearance, but I think eventually we ought to have such a classification as otherwise this continues to be a game of whack-a-mole. --- I would appreciate feedback as to whether: 1. This generally seems reasonable. 2. What appropriate next steps would be. Thanks! cc @mfreed7 @emilio @fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10039 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 March 2024 17:46:34 UTC