W3C home > Mailing lists > Public > www-style@w3.org > November 2014

Re: [css-gcpm] String-set issues

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 26 Nov 2014 09:57:02 -0800
Message-ID: <CAAWBYDC3h4aCj-2uc+1MPf4cy4-m2n-fgBH=e7s8dAwZxy8fuQ@mail.gmail.com>
To: Brad Kemper <brad.kemper@gmail.com>
Cc: HÃ¥kon Wium Lie <howcome@opera.com>, www-style list <www-style@w3.org>, Dave Cramer <Dave.Cramer@hbgusa.com>
On Tue, Nov 25, 2014 at 7:54 PM, Brad Kemper <brad.kemper@gmail.com> wrote:
>> On Nov 25, 2014, at 1:19 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>>> On Tue, Nov 25, 2014 at 12:43 AM, Brad Kemper <brad.kemper@gmail.com> wrote:
>>> Yet it isn't 'string-reset', and we don't have 'counter-set'. Maybe because
>>> 'counter-set' sounds like pushing a new kitchen counter into the mortar to
>>> set it level or something.
>>
>> Actually, we do: http://dev.w3.org/csswg/css-lists/#propdef-counter-set
>
> Gah!
>
> I don't really get why set and reset need to be two different things in that spec, so I am just going to continue to pretend that 'counter-set' doesn't exist.

Because 'reset' establishes a new scope; 'set' just adjusts the value
within a scope, like 'increment' does.  The summary sentence following
the corresponding properties should make this clear.

~TJ
Received on Wednesday, 26 November 2014 17:57:54 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:26 UTC