- From: Philip Walton <philip@philipwalton.com>
- Date: Tue, 1 Dec 2015 09:44:59 -0800
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: www-style list <www-style@w3.org>
- Message-ID: <CAGRhNhVa_zxkHCbTXrs3=6xA2voLsH1M8b_5DxznRzE9bSh50w@mail.gmail.com>
No worries, I was just checking because I'm writing an article about custom properties and want it to be factually accurate. Do have a good link I can point to where the discussion of `--` took place? It's kind of a hard thing to search for... On Mon, Nov 30, 2015 at 8:24 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > On Sun, Nov 29, 2015 at 10:34 AM, Philip Walton <philip@philipwalton.com> > wrote: > > So, the spec seem to be pretty clear about this: > > > >> Custom properties are not reset by the all property. We may define a > >> property in the future that resets all variables. > > > > The thing is, I've read comments by several people (including the spec > > editor) that specifically mention using `all: initial` for custom > property > > resetting. For example, in this Github comment Tab says: > > > >> Sure we can...that's what `all: initial` is for. (Alternately, an > >> equivalent of all for just custom properties has been proposed; it > would be > >> called --, as in --: initial.) You can then let particular custom > properties > >> thru with --foo: inherit. > > > > In addition, Firefox, Chrome Canary, and Webkit Nightly all reset custom > > property definitions when using all. > > > > So I guess in addition to the question I posed in the subject line, is > this > > a recent change? > > Note: I'm sometimes dumb and forget my own specs. The "'all' does not > reset custom properties" is an old dictate, and I forgot about it. > > I should move up my plans for a -- property then, I guess. > > ~TJ >
Received on Tuesday, 1 December 2015 17:45:29 UTC