- From: Simon Pieters via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Mar 2023 13:47:26 +0000
- To: public-css-archive@w3.org
The reason `push-button` and `square-button` were included was that they were being used somewhat frequently:
- [-moz-appearance values](https://gist.github.com/zcorpan/1a5d0dc3279a3495e14f53f2b16fa1e4)
- [-webkit-appearance values](https://gist.github.com/zcorpan/191f7d0183b7b41c8d44fc6fe12ac0d7)
- [both -moz-appearance and -webkit-appearance with different values](https://gist.github.com/zcorpan/499ee4e1f8f1a60f13e0fe43bcfb7fdf)
However, the impact of dropping them is likely minimal since they only have an effect on elements that are buttons, and also aren't styled in a way that makes `appearance` act like `none` (e.g., a border is specified). That is, it would only affect a situation like:
```
input { appearance: none; /* basically no other styles */ }
input[type=button] { appearance: push-button; }
```
For `slider-horizontal` and `slider-vertical`, IIRC that was kept in as a way to not regress horizontal/vertical rendering of sliders until a better mechanism was specified for that purpose. It has an effect in Chromium and WebKit (but not in Gecko): https://software.hixie.ch/utilities/js/live-dom-viewer/saved/11364
--
GitHub Notification of comment by zcorpan
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8506#issuecomment-1462099000 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 March 2023 13:47:28 UTC