Re: [css-writing-modes][naming] Inheritance of text-combine

fantasai wrote:

>> > The earliest revisions of this feature didn't have any automatic
>> > composition, and so the property did not inherit -- because it
>> > indicated that the entire contents of this element should be
>> > composed.
>> >
>> > However, doing automatic composition requires an inherited property.
>> > Although we first had only the manual composition ability, Koji and
>> > I had sketched out the idea of in the future, expanding
>> > 'text-combine' be a shorthand setting 'text-combine-all' and
>> > 'text-combine-auto', which would introduce the auto- composition
>> > abilities.
>> >
>> > Since we're combining both abilities in the spec right now, I think
>> > we need to make this property split now. (We will still encourage
>> > authors to use the shorthand, since that will give correct behavior.)
>>  I'm somewhat confused, the primary use case of tatechuyoko in Japanese
>>  vertical text is for simple combinations of digits. Why is there a
>>  need for more complex composition?  Wouldn't an inline block using a
>>  different writing mode be equivalent?
> No, it's not equivalent. The need for 'all' is to do anything other
> than digits. :) Also it's being used currently for EPUB.

So what's the use case for complex composition?  I'm having trouble
seeing why we need to worry about complex compositions and inheritance
given that tatechuyoko spans are typically two or three characters

>>  I'm not at all clear as to what the "auto" vs. "manual" distinction is
>>  here.  You're distinguishing the behavior of the 'all' value from the
>>  'digits' value?
> Yes. The 'all' value needs to know what element set it, and inheriting
> it confuses the issue. The 'digits' value needs to inherit to work
> properly.

I think it would be simpler to have 'text-combine-horizontal' not
inherit. I don't think 'digits' needs to inherit unless there's a very
clear use case where this is needed.


John Daggett

Received on Wednesday, 10 July 2013 03:23:15 UTC