W3C home > Mailing lists > Public > www-style@w3.org > June 2015

[css-cascade] bikeshedding "default"

From: François REMY <francois.remy.dev@outlook.com>
Date: Sat, 20 Jun 2015 22:33:55 +0200
Message-ID: <DUB405-EAS288E66385E3198E82990399A5A30@phx.gbl>
To: "'fantasai'" <fantasai.lists@inkedblade.net>, <www-style@w3.org>
> WE NEED YOUR HELP to get to CR, Cascading L4 has one major open issue:
> the keyword name 'default' conflicts with a value of the 'cursor' property
>    http://www.w3.org/TR/CSS21/ui.html#cursor-props
> So we need a new keyword. Opinions and suggestions welcome. Prior
> discussion at https://lists.w3.org/Archives/Public/www-
> style/2015Apr/0329.html (But please read the spec and do your own
> brainstorming before reading all our bad suggestions.)
>
> For the CSS WG,
> ~fantasai

I just would like to remind the working group of this brainstorming which already happened on Twitter:
https://twitter.com/csswg/status/592663652223873027


Suggestions there included (in the order in which they were proposed):

- "parent-default"
- "origin-default"
- "get-me-back-to-where-I-was-before-I-messed-with-it"
- "native"
- "cascade-default"


I also proposed to just unify this with "initial" and allow to specify where you want to backtrack:
- "initial(of-previous-origins)"
- "initial(of-useragent)"
- "initial(of-property)"
   ^ the last one is the default when you just write "initial" without arguments


Other ideas I've just now:

- "cascade-to-next-origin"
- "as-in-next-origin"
- "rollback-origin"
- "undefined" (if the value of a property is undefined in an origin, we use the value of the previous origin)
   ^ then we can just say that the initial value of a property in any level is "undefined" except the ua level where it has some value


Best regards,
François
Received on Saturday, 20 June 2015 20:34:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:54 UTC