ColumnBalancer: Don't leak the break-after value from the previous sibling to children.

ColumnBalancer: Don't leak the break-after value from the previous sibling to children.

The break-after value of an object should only be considered and joined with
the break-before value of the next in-flow sibling. Said sibling should not let
its children see this value, or anything like that. Doing that might trick the
balancer into believing that we have more forced breaks than what we actually
have.

So there's no point in storing this state as a member in ColumnBalancer. Keep
it local to each object instead.

BUG=605902
Committed: https://crrev.com/f9ae8afc886232819001f274825a6c55d7fc8482
Cr-Commit-Position: refs/heads/master@{#389144}

[mstensho (USE GERRIT), 2016-04-22 15:13:05]

mstensho@opera.com changed reviewers:
+ eae@chromium.org, leviw@chromium.org, szager@chromium.org,
wkorman@chromium.org

[eae, 2016-04-22 16:52:54]

LGTM

[eae, 2016-04-22 16:53:01]

The CQ bit was checked by eae@chromium.org

[commit-bot: I haz the power, 2016-04-22 16:53:19]

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

[commit-bot: I haz the power, 2016-04-22 17:02:39]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-22 19:48:55]

Description was changed from

==========
ColumnBalancer: Don't leak the break-after value from the previous sibling to
children.

The break-after value of an object should only be considered and joined with
the break-before value of the next in-flow sibling. Said sibling should not let
its children see this value, or anything like that. Doing that might trick the
balancer into believing that we have more forced breaks than what we actually
have.

So there's no point in storing this state as a member in ColumnBalancer. Keep
it local to each object instead.

BUG=605902
==========

to

==========
ColumnBalancer: Don't leak the break-after value from the previous sibling to
children.

The break-after value of an object should only be considered and joined with
the break-before value of the next in-flow sibling. Said sibling should not let
its children see this value, or anything like that. Doing that might trick the
balancer into believing that we have more forced breaks than what we actually
have.

So there's no point in storing this state as a member in ColumnBalancer. Keep
it local to each object instead.

BUG=605902

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

[commit-bot: I haz the power, 2016-04-22 19:48:56]

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