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

Re: [css-text] Arabic letters connecting between elements with display: inline

From: fantasai <fantasai.lists@inkedblade.net>
Date: Tue, 22 Jul 2014 06:17:24 -0700
Message-ID: <53CE6464.3090303@inkedblade.net>
To: www-style@w3.org
CC: "public-i18n-bidi@w3.org" <public-i18n-bidi@w3.org>, WWW International <www-international@w3.org>
On 05/21/2014 10:38 PM, fantasai wrote:
> Wrt http://www.w3.org/mid/52F545A0.7050001@inkedblade.net
> So, for this issue I'm seeing three possible options:
>    1. Authors can add :before, :after { content: [zwnj]; } rules.
>    2. UAs can disable joining across nonzero padding/margin/border.
>    3. Add a new property that controls this.
> The CSSWG seems to lean towards #1. Are there reasons to choose
> #2 or #3 instead?

 From discussions with i18n, it was preferred if the author doesn't
have to do anything special for cases where cases where joining
should break. So this leaned towards disabling joining due to either
bidi isolation or nonzero margin/border/padding.

However distinguishing between zero and nonzero margin/border/padding,
while a reliable heuristic that would probably work in nearly 100% of
cases, creates a behavior discontinuity at 0.

bzbarsky pointed out that changes in vertical-align would also
require a break in joining, for example, for superscripts.

So, here's the proposal:

Arabic joining across inline element boundaries is disabled if
(and only if):
   A. the boundary is also a bidi isolation boundary
   B. or, vertical alignment does not match

Alternative proposal is to add
   C. or, there is non-zero margins, border-width, or padding

Received on Tuesday, 22 July 2014 13:18:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:44 UTC