w3c / w3c/element-timing

Specify the mapping of containing block to element

Open
#30 5 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

With respect to the proposal to use "nearest containing block ancestor" as the way to aggregate text nodes:

The containing block is a rectangle, not an element, and the mapping between rectangles and elements is not trivial

  1. a single element can map to multiple containing blocks,
  2. a single containing block might not map to any specific element at all (e.g. this is what you get if a table-row cell contains several block-and-text children: you get an anonymous table-cell box which determines the containing block for those blocks-and-text, but that box does not correspond to any elements).

Can we specify the mapping from containing blocks to elements?

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 by reading the proposal's use of the nearest containing block ancestor and the CSS containing-block cases described in the issue. Compare element-to-box and anonymous-box scenarios, then define an unambiguous mapping that covers the listed cases. Done means the specification states how containing blocks map to elements.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.