This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Currently, in Rendering/Lists section, there are many declaractions of list-style-type property. Since in the new spec "CSS counter styles" [COUNTERS], all builtin styles except none and decimal can be overridden by author, I think it might be better to make it clear that whether author-defined counter style with the same name used here could affect these style declaraction of html elements. [COUNTERS] http://dev.w3.org/csswg/css-counter-styles/
Tab, what should I do here?
Xidorn's just asking for an informative note that, say, replacing the 'upper-alpha' counter style will affect rendering of <ol type=A> elements. Nothing needs to be done normatively.
(In reply to Tab Atkins Jr. from comment #2) > Xidorn's just asking for an informative note that, say, replacing the > 'upper-alpha' counter style will affect rendering of <ol type=A> elements. > > Nothing needs to be done normatively. Not exactly. I supposed that author-defined counter styles would not affect the 'type' attribute. Therefore I was suprised when I saw the behavior is defined using CSS. Though, I'd welcome the behavior that author-defineds affect, since it could simplify the impl.
The HTML spec defines <ol type=A>, etc in terms of a CSS list-style-type rule, so the fact that "@counter-style upper-alpha {...}" would affect that seems to fall out of what's defined.
It seems weird that you can redefine spec-defined counter types, but that's your call. If it's going to be allowed, I agree that it makes sense that it would affect <ol type>.
I guess I'll add a note to the <ol> section saying that this relies on CSS and you can override the counter styles which will indirectly affect the type="" attribute, just like you could directly override it with list-style-type.
(In reply to Ian 'Hixie' Hickson from comment #6) > I guess I'll add a note to the <ol> section saying that this relies on CSS > and you can override the counter styles which will indirectly affect the > type="" attribute, just like you could directly override it with > list-style-type. That's fine. One problem I am aware of is that, the word "override" has a different meaning in counter styles spec. To avoid confusion, I suggest using "redefine" before "the counter styls" instead.
Thanks. Will do.
Added. (Change will be in a future update to the spec, rolled up with some other fixes. I'm debugging my pipeline today and so can't publish just this change right now.)