W3C home > Mailing lists > Public > www-style@w3.org > April 2012

Re: [css3-values] use cases and the design of 'cycle()'

From: L. David Baron <dbaron@dbaron.org>
Date: Tue, 24 Apr 2012 09:20:06 -0700
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: "Kang-Hao (Kenny) Lu" <kennyluck@csail.mit.edu>, WWW Style <www-style@w3.org>
Message-ID: <20120424162006.GA28535@crum.dbaron.org>
On Monday 2012-04-23 13:07 -0700, Tab Atkins Jr. wrote:
> Heya Kenny!
> Below are our responses to the issues you raised in this thread.
> Issue 13: cycle() can't skip levels, or easily refer to non-inherited properties
> Issue 14: Example UA stylesheet using cycle() for <ul> is incorrect.
> Issue 15: Value equality of components of cycle() ill-defined
> Closed as OutOfScope pending WG resolution - we proposed punting
> cycle() to level 4 so we can address these and other issues with the
> design of the spec properly.

Where are "issue 13", "issue 14" and "issue 15" described?

> In particular, we currently expect something like the following in
> level 4: the current functionality of cycle() is renamed to toggle(),
> with the value equality better defined, or perhaps with the values
> restricted so as to make equality easier; a new cycle() function which
> operates like I describe in this thread (take an ident, and look for
> ancestors using the same ident to select your index into your value
> list), which solves your issue 13 and 14.

I really don't like this "look for ancestors" thing (though, again,
I'd like to see a reference to what it actually is); I think it
makes the behavior here much more complex.


𝄞   L. David Baron                         http://dbaron.org/   𝄂
𝄢   Mozilla                           http://www.mozilla.org/   𝄂
Received on Tuesday, 24 April 2012 18:20:58 UTC

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