- From: Simon Pieters via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Jan 2019 19:30:30 +0000
- To: public-css-archive@w3.org
Minutes from TPAC
https://lists.w3.org/Archives/Public/www-style/2018Dec/0003.html
This discussion ended up at a point with a statement from @frivoal that we didn't have time to address.
> zcorpan: My understanding is that all the elements with an
appearance, we'd specify a value for those.
florian: That's not what François or Ian said.
Let's back up. Ian said
> iank: I think we'd like to reduce the number of values we currently
support.
iank: Last week tkent (maybe?) added some high-precision
use-counters to track these.
iank: So in about 3 months time we'll have very accurate usage data.
This does not say anything about values in the UA stylesheet, only the set of values that the property supports.
[Chromium's UA stylesheet](https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/html/resources/html.css) has these values for elements:
`button`, `textfield`, `searchfield`, `textarea`, `push-button`, `slider-horizontal`, `checkbox`, `radio`, `square-button`, `menu-list`, `listbox`, `meter`, `progress-bar`
...and also has some other values for some internal pseudo-elements (that arguably should not be exposed to web authors).
These values, even including those for pseudo-elements, are already a subset of [the supported set of values](https://developer.mozilla.org/en-US/docs/Web/CSS/appearance). Therefore, it doesn't follow that reducing the set of supported values would necessarily mean removing any of the above values.
--
GitHub Notification of comment by zcorpan
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3024#issuecomment-453223498 using your GitHub account
Received on Thursday, 10 January 2019 19:30:31 UTC