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

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

From: Florian Rivoal <florian@rivoal.net>
Date: Fri, 10 Apr 2015 17:33:34 +0200
Message-Id: <BDED8CEF-277C-4826-AC9C-61AD720B2D69@rivoal.net>
Cc: Tantek Çelik <tantek@cs.stanford.edu>
To: www-style list <www-style@w3.org>
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.

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, then implementations must render an ellipsis/string


 - Florian
Received on Friday, 10 April 2015 15:33:59 UTC

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