- From: Nicolas Lesbats <nlesbats@etu.utc.fr>
- Date: Sat, 29 May 1999 16:43:32 +0200 (MET DST)
- To: "L. David Baron" <dbaron@fas.harvard.edu>, www-style@w3.org
On Sat, 29 May 1999, L. David Baron wrote: | However, I think it might even be better to have a slightly more | powerful feature: cycle(), which could take any number of arguments. | | So if the declared value for the property on a given element is | cycle(x1, x2, ... xn), then: | | * if the value of the property on the parent is *none* of x1...xn, the | value on the element is x1 | * if the value of the property on the parent is xk, then the value on | the element is x(k+1), unless k=n, in which case the element gets | value x1 For me it's a good solution, but if you have more than two arguments, what will be the UA behavior if some arguments are the same ? For example, if you have 'color: cycle(red, blue, red, green)' (which are possible, logical values), you will have to know the property on the grand-parent to respect the cycle. Which a so complex property, I don't think that a lot of UAs will implement this feature... A easy solution : only different values would be allowed... :-) at least in a first time... | This could be used in other ways: | | font-style: cycle(italic, normal); /* is italic if parent is oblique */ I think that a 'font-style: cycle(normal, italic)' would be more appropriate to define a tag such as <em>, since a lot of UAs render 'italic' and 'oblique' as the same. In fact, this is maybe what you want to say by "in other ways"... | list-style-type: cycle(disk, square, circle); /* something like typical UL*/ Yes, this is really fine ! | font-weight: cycle(700,900); | | Hopefully this hasn't been brought up already, since I'm only half | done digging through my email from yesterday. | | David | | L. David Baron Freshman, Harvard dbaron@fas.harvard.edu | Links, SatPix, CSS, etc. < http://www.fas.harvard.edu/~dbaron/ > | WSP CSS AC < http://www.webstandards.org/css/ >
Received on Saturday, 29 May 1999 10:43:44 UTC