- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Dec 2023 19:05:08 +0000
- To: public-css-archive@w3.org
> * I don't like either `base` (could refer to base URLs or other) or `interoperable` (things should generally be interoperable). Maybe something like `basestyle` or `stylable`? I kind of like `basestyle` - it says that it's related to styles, and it has "base" which I like for some reason. I don't like `stylable` for two reasons - there are two spellings (also `styleable`) and all controls are stylable in some ways even if they don't have *interoperable* styling which is what this attribute implies. > * Why is a pseudo-class needed if it only checks the presence of an attribute? The pseudo class allows for feature detection - it should only match when the attribute is actually supported on a given element. I.e. `const supported = document.createElement('select').matches(':basestyle');`. If there's a better way to do feature detection element-by-element, I think that'd be fine too. > * It seems to me the former has to be chosen, or it was moot to use an attribute. I don't understand this comment, sorry. -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5998#issuecomment-1866800451 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 December 2023 19:05:11 UTC