Re: [csswg-drafts] [css-ui] Unprefix 'appearance' and/or make the spec web-compatible

I'm not sure I understand what you propose doing. As far as I understand, both Webkit/chromium and gecko fully describe the look of all form controls using the appearance property on elements and their pseudos, using the UA stylesheet. Either we've got the full set, and we can use the property that way, or we don't we need to explain form controls differently.

An appearance property that only has a subset of the value wouldn't work the same way as the webkit (or moz) prefixed one. Not just in the sense that it lacks values, but the way it works in general would have to be different.

For instance, let's say we have an appearance property that only `none`, `button`, `checkbox`, and `fieldset`. What's the computed value on `<input type=search>`?
* If it's something like `auto`, we're back the the spec's proposal. Which I think is a reasonable approach, but it not what browsers are currently doing.
* If it's a value specific to the element (`searchfield`?), then we need the full list that describes every form control, and for every single one of them agree if it is fully described by a single value on the element, or if you also need pseudo elements to described subcomponents. Like the little "x" that chrome gives you to clear the content of a `<input type=search>` using `::-webkit-search-cancel-button { -webkit-appearance: searchfield-cancel-button; }`: do you have to have that pseudo and that value, or can/must it be implied by `appearance: searchfield`?
* If there's no computed value, then the property is something like a shorthand, but a shorthand to what?

I think we can get away with specifying the webkit prefixed one as a shorthand to something, and leave the something to later.

But we'll eventually need to come back to what that is, and I suspect a property with an auto value is a much more standardizable answer than a giant list that needs to cover for every variation of every form control on every platform.

GitHub Notification of comment by frivoal
Please view or discuss this issue at using your GitHub account

Received on Thursday, 30 August 2018 15:21:20 UTC