Re: [css3-ui] overflow-text and scrolling (Issue 59, related to issue 24)

> On 18 Nov 2014, at 22:57, Florian Rivoal <florian@rivoal.net> wrote:
> 
> 
>> On 18 Nov 2014, at 22:13, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>> 
>> On Tue, Nov 18, 2014 at 1:08 PM, Robert O'Callahan <robert@ocallahan.org> wrote:
>>> I'd like to keep the Gecko behavior, as it may not be Web-compatible to
>>> suddenly start displaying ellipses at the start of the line for single-value
>>> text-overflow, and I don't think shipping an experiment to find out is
>>> worthwhile.
>> 
>> [regarding the "single-value text-ellipses means only the end edge
>> gets ellipsized, even when the content has been scrolled to overflow
>> off the start edge" issue]
>> 
>> I think that's fine.

Found an older mail from Tantek (http://lists.w3.org/Archives/Public/www-style/2011Sep/0504.html) saying that single value text-overflow needs to be only on the line-end for web compat reasons. So we have our answer, and the only thing left to do is to disambiguate the spec, which can be done like this:

diff --git a/css-ui/Overview.bs b/css-ui/Overview.bs
--- a/css-ui/Overview.bs
+++ b/css-ui/Overview.bs
@@ -1226,7 +1226,9 @@ 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,
-then implementations should render an ellipsis/string in place of
+and the computed value of 'text-overflow' is one of the 2-value combinations with the first value something else than ''clip'',
+then implementations must render an ellipsis/string in place of
 the clipped content,
 with the same details as described in the value definition above,
 except that the ellipsis/string is drawn in the <a>start</a>



(I've noted this proposed resolution in the issue wiki)

 - Florian

Received on Wednesday, 10 December 2014 15:58:14 UTC