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

Re: [css3-lists] upper-hexadecimal vs. hexadecimal & text-transform

From: Øyvind Stenhaug <oyvinds@opera.com>
Date: Tue, 22 Nov 2011 18:10:52 +0100
To: Christoph Päper <christoph.paeper@crissov.de>, "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: "W3C Style" <www-style@w3.org>
Message-ID: <op.v5cx0elnbunlto@oyvinds-desktop>
On Tue, 22 Nov 2011 17:34:03 +0100, Tab Atkins Jr. <jackalmage@gmail.com>  
wrote:

> Of the remaining, in Chrome the manual ::before-based ones respect
> text-transform.  The ones that use normal markers and put
> text-transform on the list or list-item don't, but I suspect that's
> because we manually reference a shortlist of properties when
> generating the markers manually, and text-transform isn't on that
> list.  When they become "real" pseudo-elements as ::marker, they
> should receive all the properties through inheritance like normal.
> Firefox and Opera are the same, but IE honors text-transform in all
> the cases it can (just not when it's specified on ::marker, again
> because that's not yet recognized).

In a somewhat recent list marker fixup (should be present in Opera Next)  
we actually consciously avoided inheriting things like text-transform  
because we figured it would be unexpected to have e.g.  
list-style:lower-roman overridden by text-transform:uppercase.

-- 
Øyvind Stenhaug
Core Norway, Opera Software ASA
Received on Tuesday, 22 November 2011 17:11:22 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:46 GMT