W3C home > Mailing lists > Public > www-style@w3.org > November 2011

[css3-lists] Should some properties not inherit into markers?

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 23 Nov 2011 09:44:19 -0800
Message-ID: <CAAWBYDBQ7=4q2S1mP_PEHEvu5Uj5fLDHG-vC-crju-BwxuQKtQ@mail.gmail.com>
To: www-style list <www-style@w3.org>
√ėyvind brought up in another thread that some browsers block some
properties from inheriting into list markers.  His cursory testing
produced this list:

> text-transform: applied by IE
> font-style, font-weight, font-family: applied by all
> font-variant: applied by IE and WebKit
> text-decoration: applied for 'inside' only by Fx3.6 and Opera Next (seemed
> to make some sense but we'll probably revert this now that we're the odd one
> out)
> letter-spacing: applied by all except Fx

I suspect that most other properties are inherited normally.

The only ones from this list that seem potentially worth looking into
are text-transform and font-variant.

I think it's reasonable to block text-transform.  It converts between
glyphs, and the exact glyphs used (particularly uppercase vs lowercase
in bicameral scripts) is often important for list counters.  We have
uppercase and lowercase variants of all the styles that it makes sense
for already.

On the other hand, I think font-variant should inherit.  CSS 2.1 only
had one interesting value, small-caps, which is similar enough to the
text-transform values that I can see why it might have seemed
reasonable to block.  However, Fonts 3 introduces a *bunch* more
values which seem valuable to propagate into markers to ensure a
consistent appearance between the markers and the text.

So, I propose adding "::marker { text-transform: initial; }" to the
Lists 3 UA stylesheet.  Thoughts?

Received on Wednesday, 23 November 2011 17:45:09 UTC

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