Don't always have to relayout a child when fragmentainer height is unknown.

Don't always have to relayout a child when fragmentainer height is unknown.

Fragmentainer height is unknown in the first multicol layout pass, before
the initial balancing attempt. It also happens when we have to restart the
column balancing algorithm (due to dynamic content change, containing block
logical width change, etc.). In this case we only need to relayout if the child
did previously break (because then there may be pagination stuts inside that we
need to clear).

Committed: https://crrev.com/4de05710061fa25ca300b18d7ade421161ebe87a
Cr-Commit-Position: refs/heads/master@{#429135}

[mstensho (USE GERRIT), 2016-11-01 18:24:15]

The CQ bit was checked by mstensho@opera.com to run a CQ dry run

[commit-bot: I haz the power, 2016-11-01 18:24:39]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[mstensho (USE GERRIT), 2016-11-01 20:13:36]

mstensho@opera.com changed reviewers:
+ eae@chromium.org

[eae, 2016-11-01 20:47:26]

LGTM

[commit-bot: I haz the power, 2016-11-01 21:31:00]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-11-01 21:31:01]

Dry run: This issue passed the CQ dry run.

[mstensho (USE GERRIT), 2016-11-01 22:20:10]

The CQ bit was checked by mstensho@opera.com

[commit-bot: I haz the power, 2016-11-01 22:21:15]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-11-01 22:28:42]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-11-01 22:30:42]

Description was changed from

==========
Don't always have to relayout a child when fragmentainer height is unknown.

Fragmentainer height is unknown in the first multicol layout pass, before
the initial balancing attempt. It also happens when we have to restart the
column balancing algorithm (due to dynamic content change, containing block
logical width change, etc.). In this case we only need to relayout if the child
did previously break (because then there may be pagination stuts inside that we
need to clear).
==========

to

==========
Don't always have to relayout a child when fragmentainer height is unknown.

Fragmentainer height is unknown in the first multicol layout pass, before
the initial balancing attempt. It also happens when we have to restart the
column balancing algorithm (due to dynamic content change, containing block
logical width change, etc.). In this case we only need to relayout if the child
did previously break (because then there may be pagination stuts inside that we
need to clear).

Committed: https://crrev.com/4de05710061fa25ca300b18d7ade421161ebe87a
Cr-Commit-Position: refs/heads/master@{#429135}
==========

[commit-bot: I haz the power, 2016-11-01 22:30:42]

Patchset 1 (id:??) landed as
https://crrev.com/4de05710061fa25ca300b18d7ade421161ebe87a
Cr-Commit-Position: refs/heads/master@{#429135}