775628 - (css-break-3) [META] Implement CSS Fragmentation Module Level 3

Status: NEW

(Core :: Layout, enhancement, P3)

Description

[fantasai]

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).

Comment 1

[Jet Villegas (inactive)]

To Mats per Q3 Goals

Comment 2

[fantasai]

Adding bug 616402: correctly handling margins at page breaks

Comment 3

[Jen Simmons [:jensimmons]]

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.

Comment 4

[Jonathan Watt [:jwatt]]

Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)

Comment 5

[Jonathan Kingston [:jkt] he/him]

This appears to be implemented in all other major browsers now and likely will become a webcompat issue with column based layouts etc.

Comment 6

[John]

I contribute to a text editor project that allows users to create multi-column layouts, and we have to regularly tell users that we can only support Chrome largely due to Firefox not fully supporting columns. Not just users authoring documents, but also anyone visiting those documents. Of the several column features most critical, it is the ability to force a column break after an element that is likely the biggest blocker for us (break-after: column).

Comment 7

[Sebastian Zartner [:sebo]]

John, then you should follow bug 549114, which is part of this one.

Sebastian