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

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

From: Florian Rivoal <florian@rivoal.net>
Date: Tue, 18 Nov 2014 22:57:33 +0100
Cc: Robert O'Callahan <robert@ocallahan.org>, www-style list <www-style@w3.org>, Tantek Çelik <tantek@cs.stanford.edu>
Message-Id: <51D8B309-6FF1-448E-8858-38EE4B65D0D5@rivoal.net>
To: "Tab Atkins Jr." <jackalmage@gmail.com>

> 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.

I think I would prefer the alternative, and suspect that it is rare enough that changing it would’t break much content even if it does turn out to be incompatible. As you pointed out, the scrollable overflow + text-overflow combination is pretty rare.

At the same time, I understand not wanting to spend much energy on figuring out, and authors may explicitly ask for ellipses on both sides if they want to by using the 2 value variant, so I am not going to insist.

Either way, the spec needs to be clarified, as it can currently be read both ways.

 - Florian
Received on Tuesday, 18 November 2014 21:57:57 UTC

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