- From: Simon Pieters via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Sep 2018 08:56:15 +0000
- To: public-css-archive@w3.org
> Here's what I suggest we do: > > 1. Spec both `-webkit-appearance` and `appearance` > 2. Limit the values of `-webkit-appearance` to `none` and the values needed for web compat, using those listed in https://compat.spec.whatwg.org/#css-non-aliased as a starting point > 3. Do **not** define that `-webkit-appearance` has an initial value. Instead, define it as a shorthand of `appearance`. This means `appearance` may have values that cannot be expressed in `-webkit-appearance` (as needed for the UA stylesheet), and `-webkit-appearance` can be limited to the values that are required for web compat. > 4. Define the values of `appearance` to be, `none`, `auto`, plus all the values that `-webkit-appearance` has. > 5. Make `auto` the initial value of `appearance` > > Optional steps: > > 1. If we only care about the web compat values for the sake of undoing an earlier `none`, and not for the sake of turning any arbitrary element (including form controls) into any other arbitrary form control, we can define that the effect of the compat values is the same as auto. > 2. If we need it for compat reasons on the OM, we could make `auto` compute to `none` on non form controls. > 3. If we need it for compat reasons on the OM, we could make `auto` compute to the appropriate web compat value on the appropriate form controls. This seems unnecessarily complicated to me. It seems simpler to support the values necessary for web compat, and have -webkit-appearance be a simple alias, and I think that also matches web developers' expectations better (if -webkit-prefixed stuff is an indication). Do you have implementer buy-in for what you suggest? -- GitHub Notification of comment by zcorpan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3024#issuecomment-420567828 using your GitHub account
Received on Wednesday, 12 September 2018 08:56:17 UTC