- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Sun, 29 Dec 2019 15:00:43 +0000
- To: public-css-archive@w3.org
frivoal has just labeled a pull request from jugglinmike for https://github.com/w3c/csswg-drafts as "css-ui-4": == [css-ui] Hide proprietary appearance values #3968 == This is an attempt to implement the following suggestion from gh-3968: > The only changed required is that the appearance property on those pseudos must return a value that is supported by the property, and that is absolutely logical and shouldn't require any specific text except maybe a note; browsers who support special values internally can convert those values to 'auto' if those pseudos currently have a proprietary value today (either for real, or just for gCS purposes). However, in gh-3980, the motivating use case is under discussion. Depending on how that is resolved (e.g. by disabling access to non-standard pseudo-elements), this change may not be necessary. Even in that case, standardizing this behavior could improve consistency in a more immediate timeframe. The text I've written feels primitive to me, but I can't think of a better way to normatively handle a disallowed situation. For instance, it would be cleaner to allow UAs to extend the set of valid values, but that would also allow authors to use apply those proprietary values in their own code. That doesn't seem like what's desired here. An alternative to the property's computed value may be [CSSOM's definition of "resolved value"](https://drafts.csswg.org/cssom/#resolved-value). That's a little more indirect, but indirection may be warranted for an edge case like this. /cc @FremyCompany @zcorpan See https://github.com/w3c/csswg-drafts/pull/3985
Received on Sunday, 29 December 2019 15:00:45 UTC