- From: Krzysztof Maczyński via GitHub <sysbot+gh@w3.org>
- Date: Sun, 15 Sep 2024 16:15:35 +0000
- To: public-css-archive@w3.org
Maybe it should be contingent on the value of `appearance`, so that in the future, when an alternative, possibly better rendering of `select` is implemented without this part, authors can choose. This opens, it seems to me, a path to the desired by many commenters forward compatibility. (But carves in stone the currently planned variant with the part, so that, even if one day considered legacy, implementations will have to continue supporting it.) In general, each model of some control type with some innards exposed would need its own value of `appearance`. And if a need arises, multiple can exist for the same control type. And two values of `apperarance` would always be available. Namely, `none`, which gives an element no special rendering of parts, and default (`auto`?) with no parts but with possibly some special implementation-dependent rendering (satisfying some quite general constraints) and a limited set of applicable CSS properties. -- GitHub Notification of comment by ByteEater-pl Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10775#issuecomment-2351660851 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 15 September 2024 16:15:35 UTC