Only honor break-* values when appropriate.

Only honor break-* values when appropriate.

Only honor column-specific break property values if inside a multicol
container, and only honor pagination-specific break property values if inside
some kind of pagination container (printing or paged overflow).

For breaking inside paged overflow containers, honor page values, not column
values. The paged overflow implementation sits on top of the multicol
implementation, which means that it's flowthread-based. But that's just an
implementation detail. Paged overflow containers don't establish columns -- it
establishes pages. Had to update one test, since it relied on
-webkit-column-break-* working inside a paged overflow container, which no
longer is the case. Some unit tests needed an update too.

R=leviw@chromium.org
BUG=223068
Committed: https://crrev.com/f307247b890c281aee1cc7e6382c0ddb5d760abf
Cr-Commit-Position: refs/heads/master@{#380797}

[mstensho (USE GERRIT), 2016-03-04 14:54:19]

Description was changed from

==========
Only honor break-* values when appropriate.

Only honor column-specific break property values if inside a multicol
container, and only honor pagination-specific break property values if inside
some kind of pagination container (printing or paged overflow).

For breaking inside paged overflow containers, honor page values, not column
values. The paged overflow implementation sits on top of the multicol
implementation, which means that it's flowthread-based. But that's just an
implementation detail. Paged overflow containers don't establish columns -- it
establishes pages. Had to update one test, since it relied on
-webkit-column-break-* working inside a paged overflow container, which no
longer is the case.

R=leviw@chromium.org
BUG=223068
==========

to

==========
Only honor break-* values when appropriate.

Only honor column-specific break property values if inside a multicol
container, and only honor pagination-specific break property values if inside
some kind of pagination container (printing or paged overflow).

For breaking inside paged overflow containers, honor page values, not column
values. The paged overflow implementation sits on top of the multicol
implementation, which means that it's flowthread-based. But that's just an
implementation detail. Paged overflow containers don't establish columns -- it
establishes pages. Had to update one test, since it relied on
-webkit-column-break-* working inside a paged overflow container, which no
longer is the case. Some unit tests needed an update too.

R=leviw@chromium.org
BUG=223068
==========

[mstensho (USE GERRIT), 2016-03-10 19:09:37]

@leviw: ping

[leviw_travelin_and_unemployed, 2016-03-11 22:03:20]

Sorry for the delay.

LGTM.

[mstensho (USE GERRIT), 2016-03-11 22:32:03]

The CQ bit was checked by mstensho@opera.com

[commit-bot: I haz the power, 2016-03-11 22:32:50]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1762983002/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1762983002/40001

[commit-bot: I haz the power, 2016-03-12 00:11:46]

Description was changed from

==========
Only honor break-* values when appropriate.

Only honor column-specific break property values if inside a multicol
container, and only honor pagination-specific break property values if inside
some kind of pagination container (printing or paged overflow).

For breaking inside paged overflow containers, honor page values, not column
values. The paged overflow implementation sits on top of the multicol
implementation, which means that it's flowthread-based. But that's just an
implementation detail. Paged overflow containers don't establish columns -- it
establishes pages. Had to update one test, since it relied on
-webkit-column-break-* working inside a paged overflow container, which no
longer is the case. Some unit tests needed an update too.

R=leviw@chromium.org
BUG=223068
==========

to

==========
Only honor break-* values when appropriate.

Only honor column-specific break property values if inside a multicol
container, and only honor pagination-specific break property values if inside
some kind of pagination container (printing or paged overflow).

For breaking inside paged overflow containers, honor page values, not column
values. The paged overflow implementation sits on top of the multicol
implementation, which means that it's flowthread-based. But that's just an
implementation detail. Paged overflow containers don't establish columns -- it
establishes pages. Had to update one test, since it relied on
-webkit-column-break-* working inside a paged overflow container, which no
longer is the case. Some unit tests needed an update too.

R=leviw@chromium.org
BUG=223068
==========

[commit-bot: I haz the power, 2016-03-12 00:11:47]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-03-12 00:12:51]

Description was changed from

==========
Only honor break-* values when appropriate.

Only honor column-specific break property values if inside a multicol
container, and only honor pagination-specific break property values if inside
some kind of pagination container (printing or paged overflow).

For breaking inside paged overflow containers, honor page values, not column
values. The paged overflow implementation sits on top of the multicol
implementation, which means that it's flowthread-based. But that's just an
implementation detail. Paged overflow containers don't establish columns -- it
establishes pages. Had to update one test, since it relied on
-webkit-column-break-* working inside a paged overflow container, which no
longer is the case. Some unit tests needed an update too.

R=leviw@chromium.org
BUG=223068
==========

to

==========
Only honor break-* values when appropriate.

Only honor column-specific break property values if inside a multicol
container, and only honor pagination-specific break property values if inside
some kind of pagination container (printing or paged overflow).

For breaking inside paged overflow containers, honor page values, not column
values. The paged overflow implementation sits on top of the multicol
implementation, which means that it's flowthread-based. But that's just an
implementation detail. Paged overflow containers don't establish columns -- it
establishes pages. Had to update one test, since it relied on
-webkit-column-break-* working inside a paged overflow container, which no
longer is the case. Some unit tests needed an update too.

R=leviw@chromium.org
BUG=223068

Committed: https://crrev.com/f307247b890c281aee1cc7e6382c0ddb5d760abf
Cr-Commit-Position: refs/heads/master@{#380797}
==========

[commit-bot: I haz the power, 2016-03-12 00:12:52]

Patchset 3 (id:??) landed as
https://crrev.com/f307247b890c281aee1cc7e6382c0ddb5d760abf
Cr-Commit-Position: refs/heads/master@{#380797}