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: fantasai via GitHub <sysbot+gh@w3.org>
Date: Thu, 11 Jan 2018 15:57:11 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-356971335-1515686230-sysbot+gh@w3.org>
The spec writes

> For the ellipsis value implementations must hide characters and atomic inline-level elements at the end edge of the line as necessary to fit the ellipsis, and place the ellipsis immediately adjacent to the end edge of the remaining inline content.

I think the “end edge of the line” is very clearly _not_ about the DOM order of characters. As @tantek says, the clipping is visual only. There were in fact very long discussions about this in the CSSWG, and we resolved very clearly to have this behavior. Altogether the `text-overflow` property is supposed to be a paint-time effect, not a layout-time effect.  This was not only because it is easier to implement, but because the effect is more consistent.

As for multi-line ellipsis, the text that is clipped is on later lines, and line-breaking is already logical, so there is no conflict with expectations there: later text on later lines is elided.

GitHub Notification of comment by fantasai
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2125#issuecomment-356971335 using your GitHub account
Received on Thursday, 11 January 2018 15:59:14 UTC

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