w3c / w3c/element-timing

Text nodes do not have a "border box"

Open
#33 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Bikeshed
Stars
61
Forks
19
Avg merge
1d 10h
Merged PRs (30d)
1

Description

https://wicg.github.io/element-timing/#sec-report-text step 2.1 says:

the border box of text

where text is a Text node. In CSS elements can have border boxes but text cannot. See https://www.w3.org/TR/css-display-3/#intro which defines boxes (for elements and pseudo-elements, plus anonymous boxes) and https://drafts.csswg.org/css-box-3/#border-box which defines a "border box", but only for boxes, not text runs.

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

Read the report-text section of the Element Timing specification, especially step 2.1, then compare its use of “border box” with the linked CSS Display and CSS Box specifications. The work is done when the specification’s treatment of a Text node and border-box terminology is technically consistent and the affected wording is unambiguous.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.