- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Sep 2018 05:35:34 +0000
- To: public-css-archive@w3.org
> I suggest doing (2), but allowing internal values that are only supported in the UA style sheet, not in author style sheets, to make up for default styling as necessary (including internal pseudo elements etc). > > Possibly adding the auto keyword, if you can convince @MatsPalmgren. Ok, now I see how you plan to resolve what I otherwise though was a contradiction. (I'll note that this is not mentioned in the compat spec). This has not yet been brought up in discussions in the CSSWG, so I don't know how other people feel about that. As far as I know, this notion of different abilities in the UA stylesheet and author stylesheets would be a new things as far as standards are concerned. Although I am a little skeptical, I'm open to exploring the idea, as that does indeed seem to be a solution that could work, but If we're talking not only about introducing/standardizing a new property, but also of a new mechanism in the cascade, I'd like us to be very careful and deliberate about that. For instance, what do you get out of the OM (the old style one or the typed OM) if the property has one of these values that the authors can't set? Presumably you still get that value in string or object representation, but what happens if you try to assign it back? In the string based om, presumably the same kind of failure as with any parse error, but in the Typed OM we've bypassed the parser, so do you get an exception? Probably, but which? TypeError or something more specialized? Do we break something by making it impossible to re-set the property the the value it currently has? Can you use `revert` to go back to the a value that you could not manually set? Presumably yes, but as the `revert` value is not widely implemented, how are authors supposed to cancel a `none` if revert isn't there? Is the richer set of values available in user style sheets (presumably not)? Is there any weird interaction with custom properties? Is there any weird interaction with animations or transitions? … And maybe most importantly, does that concept have other uses than this `(-webkit-)appearance` property? And in what way does this solve the problem better than the much more conventional `auto` approach? -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3024#issuecomment-421236310 using your GitHub account
Received on Friday, 14 September 2018 05:35:36 UTC