w3c / w3c/csswg-drafts

[css-break] Suggest adding new value to `box-decoration-break` to allow bounding box or a separate property to control the background.

Open
#8,535 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Regarding https://drafts.csswg.org/css-break/#break-decoration

Propose that a new value "bounds" for box-decoration-break.
"bounds" is a suggestion only, any string that conveys the intent.

The value intends to represent rendering the background-* properties such that they are applied to the bounding box of fragmentation boxes. The rendering would be limited to the fragmentation boxes.

E.g.
image

The border would be around the joined fragment boxes.

E.g.

Scenario Example
Background image
Background clipped to text which has background fragmentation image

Updated based on comment from @Loirooriol:
This suggestion applies mainly to the background portion of the box-decoration-break, so possibly this belongs as its own property/sub-property. E.g. box-decoration-break-background with values slice, clone, and bounds.

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 the CSS Break specification section linked in the issue, especially the current box-decoration-break behavior. Compare the proposed bounds value and separate background property against the illustrated fragmentation scenarios. Done means the CSS Working Group has resolved the proposal and the relevant editor draft reflects the agreed syntax and behavior.

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
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.