The default bug view has changed. See this FAQ.
Bug 775628 (css3-break)

Implement CSS Fragmentation

NEW
Assigned to

Status

()

Core
Layout
P3
normal
5 years ago
4 months ago

People

(Reporter: fantasai, Assigned: mats)

Tracking

(Depends on: 10 bugs, {dev-doc-needed, DevAdvocacy})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [DevRel:P1], URL)

(Reporter)

Description

5 years ago
Tracking bug for pagination. The initial project is

  - Finish break-inside: avoid (bug 685012)
  - Reimplement forced breaking (bug 683043)
     - Depends on refactoring nsReflowStatus (bug 775624)
  - Alias page-break-* to break-* (bug 775618)
  - Implement break-before/after: avoid (bug 775617)
  - Implement widows/orphans (bug 137367)
  - Implement break-inside: avoid-page (bug 775622)

This set of tasks includes CSS2.1 page-break-* (bug 132035) and CSS3 Multi-col breaking (bug 549114).
(Reporter)

Updated

5 years ago

Comment 1

5 years ago
To Mats per Q3 Goals
Assignee: nobody → matspal
(Reporter)

Comment 2

5 years ago
Adding bug 616402: correctly handling margins at page breaks
Depends on: 616402
(Assignee)

Updated

5 years ago
Depends on: 793686
(Assignee)

Updated

5 years ago
Depends on: 793692

Updated

4 years ago
Depends on: 883676

Updated

4 years ago
Blocks: 913153

Updated

4 years ago
No longer blocks: 913153
Keywords: DevAdvocacy
Whiteboard: [DevRel:P1]
Keywords: dev-doc-needed
Priority: -- → P3
I just saw a note on the Trello board that this is about printing websites on paper. 

^  Fragmentation is primarily about how to take a website and format it to make it printable on a standard 9.5x11 piece of paper. Not a lot of focus by other browsers. 

There are certainly properties in this spec that focus on paper. But increasingly there are other properties here, too — ones that affect author's ability to layout columns. Could we please consider staying on top of those properties, and not dismissing this as 'print-only'. I think it's accurate to say that the Fragmentation spec used to be all about printing on paper, but increasingly it's about how to handle fragmented flows in a complex layout system on screens.

The `break-inside` property is a prime example. Without it, people can't control their content inside a multicolumn layout context in the ways they need. Autoprefixer mitigates this pain for those developers who use it, but everyone else is bashing their head against this wall. I think https://bugzilla.mozilla.org/show_bug.cgi?id=775618 would get us needed properties, without much effort.
You need to log in before you can comment on or make changes to this bug.