- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Jul 2020 06:40:37 +0000
- To: public-css-archive@w3.org
The conclusion reached during the meeting is a little bit flawed, as we used imprecise language and confused ourselves. > RESOLVED: Limit 'appearance: button' to buttons once we figure out what buttons are > As a follow up on the previous discussion, we should define what buttons refer to We don't actually need to define what buttons are, because the way we achieve "Limit 'appearance: button' to buttons" is by making `button` part of the `<compat-auto>` non-terminal value type. This means the button keyword will behave identically to the `auto`, this lets widgets get their native appearance, and leaves other things alone. The result is that things that aren't supposed to be buttons can no longer forcibly be made into buttons, but we don't need to specify which is which, as determining what is the correct native appearance of various widgets is the responsibility of the host language (HTML), not of the css spec. Based on that, the resolution is actually enough to make the edit to the spec, and does not need further research to determine what buttons are. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5174#issuecomment-666957788 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 31 July 2020 06:40:39 UTC