w3c / w3c/csswg-drafts

[css-overflow-4] Clarify mandatory behavior for text-overflow with scrolling

Open
#11,291 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

css-overflow-4
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

The CSS Overflow 4 spec, Section 4.1 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 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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with CSS Overflow 4 Section 4.1, especially the ellipsis-scrolling text quoted in the issue, and review the linked Chromium bug for the interoperability context. Done means reaching a specification decision and revising the wording, if accepted, so the scrolling behavior is explicitly mandatory rather than expressed with “should”.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
documentation, web-dev
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.