w3c / w3c/csswg-drafts

[css-break] define breaking of floats

Open
#3,407 3 comments 1 reaction 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

The current breaking specification doesn't appear to define a lot of detail for breaking of floats. I think a definition ought to answer at least the following questions (which are written assuming writing-mode: horizontal-tb):

  • how do the rules for float placement interact with fragmentation, particularly when the widths of the fragments are different? For example:
    • if there are two floats at the bottom of a fragment that need to be continued in the next fragment, but they don't both fit in its width, which one goes first? (I would assume the earlier one in the document order.)
    • if a float doesn't fit within a fragment and it needs to begin in a later fragment, is it possible to place any other floats before it begins? (I would assume not.) In what order do such continued floats begin? (I'd again assume document order.)
  • If a float's containing block does not exist in the fragment in which (part of) the float is, how are the edges of that containing block defined?

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 current CSS breaking specification and its rules for float placement and fragmentation. Work through the listed cases involving differing fragment widths, continued floats, ordering, and missing containing blocks, then document decisions that define the behavior for each case.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.