- From: Axel Dahmen <brille1@hotmail.com>
- Date: Sat, 27 Mar 2010 21:04:06 +0100
- To: www-style@w3.org
> We certainly could more explicitly talk about the effects that > list-style-type has on the ::marker pseudoelement. > > No reason to think about deprecating list-style-type, though. In > addition to making it easier to type a small subset of possible > <glyph> values, it does a large number of ordered list types that are > more annoying to create explicitly with counters. Yes, you are right. I got mixed up between selectors and properties. Sorry for that... What I actually meant was to have list-style-type property become valid and common for the ::marker selector. In that case we can get rid of the content property and define a custom string using the list-style-type property, having its definition expanded by <string>. This way the look of a ::marker depended only on one single property. Not either this, or sometimes that, or other times another. See my point? Cheers, Axel Dahmen
Received on Saturday, 27 March 2010 20:04:50 UTC