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

Re: [CSSWG] Minutes and Resolutions TPAC F2F 2009-11-02: text-overflow

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 12 Nov 2009 17:29:53 -0600
Message-ID: <dd0fbad0911121529u2edacd7lef9484b3347fc85c@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: www-style@w3.org
I thought we *did* end up resolving some of the ellipsis questions
over lunch-time discussions?  Specifically, I think I ended up
convincing people pretty well that presentation-based ellipsizing was
optimal (and in the general case, the only sane thing), and further
conversation with some people who were familiar with bidi conventions
in paper text supported that.

That is, do ellipsizing by first laying out all of the text normally,
then chop off any overflowing bits and as much as is necessary to
insert the ellipsis at the end of the line.  This means, that, frex, a
run of text that is half latin and half hebrew, where the hebrew text
gets cut off halfway through, would display the latin text and the
logical end of the hebrew text, with the ellipse on the right edge
indicating the logical beginning of the hebrew section is cut off.
This is simpler to implement and, I think, to understand, and is the
only sane thing to do in the presence of scrollbars (once scrolling in
the presence of text-overflow:ellipsis is fixed to be sane).  This of
course assumes that the overriding text-direction of the paragraph is
ltr; if it was rtl, the ellipsis would be on the left and the latin
text would similarly have its logical beginning chopped off.

~TJ
Received on Thursday, 12 November 2009 23:30:47 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:22 GMT