w3c / w3c/csswg-drafts

[css-break-3] rules for direction to use when slicing inline borders for box-decoration-break:slice are unclear

Open
#4,989 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

css-break-3 i18n-tracker
Dominant language
Bikeshed
Stars
4.9k
Forks
816
Avg merge
2d 18h
Merged PRs (30d)
24

Description

The rules for joining boxes with box-decoration-break: slice currently say:

For boxes broken across lines
First, fragments on the same line are connected in visual order. Then, fragments on subsequent lines are ordered according to the element’s inline base direction and aligned on the element’s dominant baseline. For example, in a left-to-right containing block (direction is ltr), the first fragment is the leftmost fragment on the first line and fragments from subsequent lines are put to the right of it. In a right-to-left containing block, the first fragment is the rightmost on the first line and subsequent fragments are put to the left of it.

The normative text seems to say that it's the inline element's own direction, but the examples both refer to the containing block's direction. It should be clear which one is used.

(I got here as part of filing Mozilla bug 1632228.)

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 CSS Break 3 “joining boxes” section linked in the issue, then compare its normative wording with the left-to-right and right-to-left examples. The issue is done when the text unambiguously identifies which direction determines fragment ordering.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.