- From: Brad Kemper <brad.kemper@gmail.com>
- Date: Wed, 26 Nov 2014 14:07:15 -0800
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: Håkon Wium Lie <howcome@opera.com>, www-style list <www-style@w3.org>, Dave Cramer <Dave.Cramer@hbgusa.com>
> On Nov 26, 2014, at 9:57 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > > 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. Clear as mud, but that's OK. It's probably just me.
Received on Wednesday, 26 November 2014 22:07:45 UTC