[csswg-drafts] [css-overflow-4] Clarify mandatory behavior for text-overflow with scrolling (#11291)

gitspeaks has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-overflow-4] Clarify mandatory behavior for text-overflow with scrolling ==
The [CSS Overflow 4 spec, Section 4.1](https://drafts.csswg.org/css-overflow-4/#ellipsis-scrolling) states:

> When an element is scrolled (e.g. by the user, DOM manipulation), more of the element’s content is shown. The value of text-overflow should not affect whether more of the element’s content is shown or not. If a non-clip text-overflow is set, then as more content is scrolled into view, implementations should show whatever additional content fits, only truncating content which would otherwise be clipped (or is necessary to make room for the ellipsis/string), until the element is scrolled far enough to display the edge of the content at which point that content should be displayed rather than an ellipsis/string.

Firefox complies with this specification. Chrome does not follow this behavior. There is an open [bug](https://issues.chromium.org/issues/41333808) for this issue.

The reasoning provided is that the specification uses the term **should**, which is interpreted as suggestive rather than **mandatory**. Specifically:

(1)  _"The value of text-overflow should not affect whether more of the element’s content is shown or not."_

(2) _"If a non-clip text-overflow is set, then as more content is scrolled into view, implementations should show whatever additional content fits..."_

Admittedly, statement 1 initially confused me, but I interpret it to mean that `text-overflow` neither activates nor prevents scrolling. Statement 2, however, reads as "strongly encouraged."

In my opinion, the spec should be revised to explicitly make this behavior **mandatory**.


Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11291 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 28 November 2024 14:23:00 UTC