w3c / w3c/csswg-drafts

[css-break][css-box][css-text][css-position] percentages and fragmentation

Open
#6,512 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

css-break-3
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

There are a few properties where percentages are resolved against the size of the container. What if the container is fragmented? Each fragment is likely to have a different block size, and could even have different inline-sizes. How are these percentages then resolved? Per fragment? Based on the first fragment? Something else? For instance:

  • margin-*, padding-* (both have potentially multiple instances, due to box-decoration-break)
  • text-indent
  • left, right, top, bottom
  • (I'm sure there are more)

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

The issue names no files, tests, or entry points. Start by reviewing the CSS fragmentation and percentage-resolution specifications for margin/padding, text-indent, and positional offsets; done means an agreed rule for resolving percentages across fragments.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
frontend, web-dev
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.