- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Aug 2018 04:06:49 +0000
- To: public-css-archive@w3.org
It seems to me that we're talking past each other. Specifying the intersection of values that all browsers support (or possibly the subset that are actually used in web pages), as well as the values that only chrome supports but that are needed for web compat. This is not hard. However, this does not answer the question of how the property works as a whole, and we need to answer that question if we're supposed to standardize it. 1. Do we expect each browser to support the specified handful of values **plus** a gazillion proprietary values and corresponding pseudo-elements to describe the rest of form controls? 2. Do we expect the rest of form controls to be handled by a single magic value that means "do the right thing", called `auto` or `normal`? 3. Do we expect the rest of form controls to be handled by a separate mechanism, that is only overridden when the `-webkit-appearance` property is set (implying that `-webkit-appearance` isn't a regular property, but something like a shorthand, since it would otherwise have to have an effect on all elements, which brings us back to option 1 or 2)? > We might also decide to add `normal` as a keyword (instead of `auto`?) This is the approach I am pushing for, so I'm happy to go with it, but I don't see how the name of that keyword makes any difference. I'm happy to take `normal` over `auto` if that makes something easier, or even if that's a mere preference. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3024#issuecomment-417546455 using your GitHub account
Received on Friday, 31 August 2018 04:07:21 UTC