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

Re: [css3-ui] incorrect prose in text-overflow?

From: Tantek Çelik <tantek@cs.stanford.edu>
Date: Tue, 21 Apr 2015 22:57:02 -0700
Message-ID: <CAEV2_WYgepTUJ4iibntq8_mLY=xY_E8NZqr+yK2BHsweJXMc9A@mail.gmail.com>
To: Florian Rivoal <florian@rivoal.net>
Cc: www-style list <www-style@w3.org>, Tantek Çelik <tantek@cs.stanford.edu>
On Fri, Apr 10, 2015 at 8:33 AM, Florian Rivoal <florian@rivoal.net> wrote:
> I found a small problem in the text of this section:
>
> http://dev.w3.org/csswg/css-ui/#ellipsis-scrolling
>
>
>   As some content is scrolled into view, it is likely that
>   other content may scroll out of view on the other side.
>   If that content's block container element is the same
>   that's doing the scrolling, and the computed value of
>   text-overflow has two values, with the first a non-clip
>   value, then implementations must render an ellipsis/string
>   in place of the clipped content[...]
>
> This is correct for ltr text, but not for rtl text, as when using
> two values, the first is defined to be the line-left edge, not
> the start edge.

Took me a little bit to work through all the reasoning for this, but I
believe I have verified your analysis.


> Proposed mini-patch:
>
>   that's doing the scrolling, and the computed value of
> - text-overflow has two values, with the first a non-clip
> + text-overflow has two values, with
> the value of the start edge a non-clip value

That wording feels awkward to me and confusing since as you said it
depends on ltr/rtl. Trying this instead to hint that there's a level
of indirection involved:

> the value applying to the start edge being a non-clip value,

Thanks,

Tantek
Received on Wednesday, 22 April 2015 05:58:18 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:30 UTC