W3C home > Mailing lists > Public > www-style@w3.org > August 2013

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

From: fantasai <fantasai.lists@inkedblade.net>
Date: Tue, 06 Aug 2013 23:48:15 -0700
Message-ID: <5201EDAF.6070305@inkedblade.net>
To: www-style@w3.org
On 07/10/2013 05:16 AM, Koji Ishii wrote:
>
> Could you explain a bit more about how "not inherit" makes things simpler? I would like to understand its value.
>
> I know it's still before LC, but we've shipped non-inherit version one year ago, then an author reported that one real content:
>    <span style="text-combine-horizontal:all"><span>12</span></span>
> doesn't work, and we found our implementation wasn't following the spec change, so we fixed our build to inherit.
>
> So changing it back to non-inerhit will break at least one commercial content, at maximum...I don't know.
>
> Is it more valuable to change than the risk of breaking existing content?

That's an interesting case. I have some concern about handling that
while also doing something sensible with
   <span style="text-combine-horizontal:all">1<span>2</span></span>

Right now we say that TCY is disabled if there is an element boundary.
So what happens here? 1 is sideways, but 2 is upright!

~fantasai
Received on Wednesday, 7 August 2013 06:48:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 August 2013 06:48:47 UTC