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

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

From: Christoph Päper <christoph.paeper@crissov.de>
Date: Thu, 24 Nov 2011 17:38:03 +0100
Message-Id: <6AA81DAE-048B-426D-A117-C1A9DCBE5208@crissov.de>
To: www-style list <www-style@w3.org>
Tab Atkins Jr.:
> On Thu, Nov 24, 2011 at 2:04 AM, Christoph Päper
>> Tab Atkins Jr.:
>> 
>>> I think it's reasonable to block text-transform.  It converts between glyphs,
>> 
>> ‘font-variant’ changes glyphs, too. Some values of ‘text-transform’ change characters (but keep letters intact).
> 
> font-variant changes glyphs, but only to stylistic variants.

Smallcaps, although being lowercase letters, are hard to differentiate from small capitals, i.e. uppercase letters, when there’s little or no context.

> On the other hand, in bicameral scripts, the case of a marker is often important.

Actually not all that often if used correctly, because we’re talking about styles here that can always fall back to decimals.

>> 1. Predefined counter values with any of the prefixes ‘upper-’, ‘lower-’
>>    or ‘fullwidth-’ are not affected by the ‘text-transform’ property.
>> 2. There is a predefined counter value without any of these prefixes.
>>    It usually is a near-alias of the ‘lower-’ variant. The only
>>    difference is that it is affected by the ‘text-transform’ property.
>> 3. The ‘@counter-style’ at-rule either gets another descriptor to
>>    facilitate the case protection described above or … ‘letter’ …
> 
> #1 seems too magical to me.

It would just use #3. I never intended the magic to be in the prefixes per se.

> I don't believe there's a significant problem to address that needs #2, #3, or #4.

#2 should have been the default since ‘::marker’ returned, although ‘counter()’ should have three parameters then.
Received on Thursday, 24 November 2011 16:38:43 GMT

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