Re: [css-ruby][css-writing-modes] The writing-mode property on ruby internal boxes

On Thu, Jul 16, 2015 at 4:58 PM, Koji Ishii <kojiishi@gmail.com> wrote:

>
> On Tue, Jul 14, 2015 at 4:09 PM, Xidorn Quan <quanxunzhen@gmail.com>
> wrote:
>
>> I don't think it makes sense in most cases for ruby internal boxes to
>> have different writing-mode with their parent. AFAICS, the only exception
>> is inter-character ruby.
>>
>> I propose:
>>
>> In CSS Writing Mode spec, add ruby base container, ruby base, and ruby
>> text to the exception list, so that they won't be the target of
>> writing-mode property.
>>
>> In CSS Ruby spec, make ruby-position always forces the writing-mode of
>> the ruby text container. When ruby-position is over or under, the
>> writing-mode of the ruby text container is computed to the same value as
>> its parent.
>>
>
> I'm fine with this proposal. Two confirmation:
> 1. I'm not sure how much we'd see similar examples, but since the ruby
> spec came later, wouldn't it be enough to write it in the ruby spec?
>

I'm not sure about this. If the writing modes spec is more stable than the
ruby spec, I guess it is probably better to only have it in the ruby spec.
But I have no idea how this could be specified in a different spec than the
one which defines the property. Anyway, I'm not familiar with editorial
things like this.

2. When you say "forces", are you suggesting to change the computed values
> or effective values?
>

The computed values, same as what the current spec does on ruby-position:
inter-character. I don't think it makes sense to have different value for
computed one and effective one here.

- Xidorn