W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2019

[csswg-drafts] [css-overflow] It should be detectable whether an element ellipsize text (#4123)

From: blidblid via GitHub <sysbot+gh@w3.org>
Date: Wed, 17 Jul 2019 13:22:06 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-469189995-1563369725-sysbot+gh@w3.org>
blidblid has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-overflow] It should be detectable whether an element ellipsize text ==
Current spec: https://www.w3.org/TR/2018/WD-css-overflow-3-20180731/#auto-ellipsis
Chrome issue: https://bugs.chromium.org/p/chromium/issues/detail?id=980476.

The use of ```text-overflow: ellipsis``` will make overflowing text hidden from users. At the *very pixel* where the ellipsis appear, the overflow is undetectable. This means that some characters will be permanently hidden from users, and that there's no workaround for developers.

This issue only appear at the exact pixel where ellipses appear.
For some text content, rounding of scrollWidth will make queried scrollWidth, clientWidth or DOMRect identical, despite the text-overflow.

Here is a codepen where overflow appears despite ```scrollWidth == clientWidth```:

This issue makes text-overflow: ellipsis unusable in some contexts. 
For example in the healthcare, where doctors must have complete access to all information at all times.

The spec should mandate that if an element has ellipsized text, then that must be detectable.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4123 using your GitHub account
Received on Wednesday, 17 July 2019 13:22:08 UTC

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