W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2018

Re: [csswg-drafts] [css-ui] text-overflow: ellipsis when a word of different direction was truncated

From: Addison Phillips via GitHub <sysbot+gh@w3.org>
Date: Thu, 04 Jan 2018 22:58:28 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-355423470-1515106707-sysbot+gh@w3.org>
@frivoal A case could be made that the non-bidi case (that is, the unidirectional case) isn't necessarily truncating "visually", it just looks that way :-). Consider a purely right-to-left text: it should truncate on the left side rather than the right side.

@kojiishi calls out that vertical presentation is *also* affected here and needs an answer about visual vs. logical truncation. I think that shouldn't be overlooked.

If the control is a "viewport" on an infinite baseline of text, that suggests a visual presentation (visual is certainly easier in that case; particularly I'm thinking about scrolling behavior, although cursor movement might be an adventure if the cursor is placed in bidi text---the cursor normally moves logically in text)

@matial I actually treated mentally each RTL word as isolated (as we recommend for insertion), as they are inserted into an LTR context, so logical:

> the world is full of SARBEZ, HPELE ...

And visual:

> the world is full of SARBEZ, STNAH ...

GitHub Notification of comment by aphillips
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2125#issuecomment-355423470 using your GitHub account
Received on Thursday, 4 January 2018 22:58:30 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:22 UTC