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

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

From: Ian Vollick <vollick@chromium.org>
Date: Tue, 18 Nov 2014 09:58:23 -0500
Message-ID: <CAF10CM3mHDmUYHcL-s+P9EXDhQhrnN89iKjZsAcQxrC1Y1MpNQ@mail.gmail.com>
To: Florian Rivoal <florian@rivoal.net>
Cc: www-style list <www-style@w3.org>, Tantek Çelik <tantek@cs.stanford.edu>
I'm concerned about the performance implications here. If browsers have to
analyze text on every scroll update in order to place the ellipses
correctly, it'll be a lot tougher to get a fast implementation. Perhaps we
could hide/fade the ellipses during a scroll interaction and show them
afterwards?

On Tue, Nov 18, 2014 at 9:51 AM, Florian Rivoal <florian@rivoal.net> wrote:

>
> > On 18 Nov 2014, at 15:15, Florian Rivoal <florian@rivoal.net> wrote:
> >
> > "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 the clipped content, with the same
> details as described in the value definition above, except that the
> ellipsis/string is drawn in the start (rather than end) of the block’s
> direction (per the direction property).”
>
> Oh, and while we’re at it, if we decide to keep this paragraph, I suggest
> replacing the “should” in the second sentence with a “must”.
>
>  - Florian
>
Received on Tuesday, 18 November 2014 14:58:51 UTC

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