- From: Ian Hickson <ian@hixie.ch>
- Date: Sat, 13 Sep 2003 19:21:28 +0000 (UTC)
- To: "staffan.mahlen@comhem.se" <staffan.mahlen@comhem.se>
- Cc: "www-style@w3.org" <www-style@w3.org>
On Fri, 12 Sep 2003, staffan.mahlen@comhem.se wrote:
>
> The main advantage would be to simplify rendering lists inline
You wouldn't use ::marker for inline lists, unless we are talking
inline-block lists, in which case you would use inline-list-item or some
such.
> but it could possibly be useful to allow the list concept to work based
> on ::marker for other styling as well (eg h1::marker {content: normal}
> if that is considered style...).
That's already possible, just say
h1 { display: list-item; }
> This could possibly be defined something like:
> a marker pseudo element (with 'content' which is not 'inhibit') only
> generates a marker box when the display of the element is list-item
> and the list-style-position is outside, otherwise it generates a box
> that is treated as a replaced inline element.
How is that different to ::before?
> Does the above make any sense and would it be useful if so?
I don't see much use, to be honest. It's also hard to define that way
without running into troubles, although I forget exactly what the problems
I got when I tried to do it were.
> As a side note, would it be useful to add body to the below suggested
> default to capture list-item featured elements that are rendered as
> list items but are not in content an actual list-item in a list ( eg,
> h1 {display: list-item})?
>
> ol, ul { counter-reset: list-item; }
It's implied by the root element.
--
Ian Hickson )\._.,--....,'``. fL
U+1047E /, _.. \ _\ ;`._ ,.
http://index.hixie.ch/ `._.-(,_..'--(,_..'`-.;.'
Received on Saturday, 13 September 2003 15:22:10 UTC