- From: Tom Potts <karaken12@gmail.com>
- Date: Wed, 24 Jun 2015 13:18:38 +0100
- To: François REMY <francois.remy.dev@outlook.com>
- Cc: fantasai <fantasai.lists@inkedblade.net>, CSS WG <www-style@w3.org>
- Message-ID: <CAF2aeH2ffz_3EWCRaCS54DQS9UQsQ7GspEhsF9KiMMws=6sfqQ@mail.gmail.com>
I took fantasi's advice and read the spec before looking at the other suggestions, and I also came up with "rollback". It's how it's described in the spec, and I think most authors seeing a declaration of "font-size: rollback;" will think the right thing. The downsides: it's maybe a bit less discoverable than something like "default", and there's a chance that an author will think it will roll back the cascade in some way instead. "rollback-origin" might work better there, although as mentioned before "origin" is a bit of an overloaded word. Another thought was something along the lines of "undefined" (I actually thought "empty"), although I'm not sure about the baggage you're suggesting, François. I think the best one might be "unset", to be read in the passive voice; after all, it does behave as if you didn't set it. Since that's taken, maybe "not-set"? TL;DR: - rollback - empty - not-set Cheers, Tom On 20 June 2015 at 21:33, François REMY <francois.remy.dev@outlook.com> wrote: > > 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 Wednesday, 24 June 2015 12:19:28 UTC