RE: [css3-text] combining transforms

While I understand the value of @-rule, I don't understand the value of prohibiting combination from your explanations.

Let's say an author defined an @-rule to the root element so that the document looks better in vertical flow. Applying "uppercase" to a div canceling the @-rule doesn't make sense. It only makes sense when the @-rule is about case transformation.

It looks to me that prohibiting combinations simply reduces the value and general-purpose usability of @-rule. What did I miss?


-----Original Message-----
From: Florian Rivoal [mailto:florianr@opera.com] 
Sent: Tuesday, February 07, 2012 10:04 AM
To: www-style@w3.org
Subject: [css3-text] combining transforms

The text-transform property allows some simple forms of combining transforms. It is useful, but not fundamental to the way text-transform works.

My proposal for @text-transform [1] also includes a way to combine transforms, as that is needed to make a number of meaningful custom transforms.

I think that the mechanism proposed in the @-rule is more flexible. It allows control over the order in which the combined transforms are applied, which also makes it scale better as new transforms are introduced, as the author is not limited by the predefined combinations hard-coded in the spec.

I think we should therefore drop the ability to combine transforms in the property in favor of the mechanism proposed in @text-transform.

This would mean changing the grammar from:
none | [ [ capitalize | uppercase | lowercase ] || full-width || full-size-kana ]
to:
none | capitalize | uppercase | lowercase | full-width | full-size-kana

and dropping this piece of prose:

"When multiple values are specified and therefore multiple transformations need to be applied, they are applied in the following order:
‘capitalize’, ‘uppercase’, and ‘lowercase’
‘full-width’
‘full-size-kana’"

  - Florian

[1] http://wiki.csswg.org/ideas/at-text-transform

Received on Tuesday, 7 February 2012 09:45:39 UTC