W3C home > Mailing lists > Public > www-style@w3.org > July 2015

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

From: Koji Ishii <kojiishi@gmail.com>
Date: Thu, 16 Jul 2015 15:58:48 +0900
Message-ID: <CAN9ydbUpmaDUF=+PyzbUmmjUou2+9FjeaA+xwWmTQ=G7XBXPQw@mail.gmail.com>
To: Xidorn Quan <quanxunzhen@gmail.com>
Cc: www-style list <www-style@w3.org>
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?
2. When you say "forces", are you suggesting to change the computed values
or effective values?

/koji
Received on Thursday, 16 July 2015 06:59:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:18 UTC