W3C home > Mailing lists > Public > www-style@w3.org > February 2012

RE: [css3-text] combining transforms

From: Koji Ishii <kojiishi@gluesoft.co.jp>
Date: Tue, 7 Feb 2012 10:57:17 -0500
To: Florian Rivoal <florianr@opera.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <A592E245B36A8949BDB0A302B375FB4E0D3297D44B@MAILR001.mail.lan>
I noticed my last paragraph was broken, sorry about that. Allow me to rephrase.


I understand which order works the best is hard to figure out at this point, but we could take either one which we believe works better from use cases we know today, and add the other order in future if desired. Prohibiting doesn't still make sense to me.


-----Original Message-----
From: Koji Ishii [mailto:kojiishi@gluesoft.co.jp] 
Sent: Tuesday, February 07, 2012 4:17 PM
To: Florian Rivoal; www-style@w3.org
Subject: RE: [css3-text] combining transforms

I'm fine not to allow multiple custom transforms together, but I'd like it be usable between predefined and custom, and between casing and full-width.

What you're proposing looks like not to allow them, and @text-transform doesn't help in that regard at all if I understand your wiki correctly.

I understand the order is best at this point, but we could take either, and add the other order in future if desired. Prohibiting doesn't still make sense to me.


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

On Tue, 07 Feb 2012 10:39:05 +0100, Koji Ishii <kojiishi@gluesoft.co.jp>
wrote:

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

I don't want to prohibit combinations. I say we may not need two different mechanisms for combining.

> 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.

When the text-transform property is used to combine two transforms, the order in which they are applied is not under author control. It is predefined for predefined transforms. Without knowing what all transforms that are being combined are, we cannot specify in which order it is best to apply them. Because of that, I don't think the combination mechanism of the text-transform property is adequate to combine predefined transforms with custom transforms, or custom transforms together.

Since the combination mechanism in @text-transform is able to deal with all cases, thanks to leaving the order under author control, I propose that this should be the only mechanism we keep.

  - Florian

Received on Tuesday, 7 February 2012 16:03:53 GMT

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