Handle pagination breaking on rows correctly when a table has >1 section

Handle pagination breaking on rows correctly when a table has >1 section

When a table has more than one section, layoutRows() needs to have an
up-to-date logicalTop() for the section. Otherwise it will calculate
the wrong offset from the top of the page for the row when figuring out whether
to put a strut on it.

BUG=621359
Committed: https://crrev.com/5aca76371f4c851adb4b1ac398ac45d62073967b
Cr-Commit-Position: refs/heads/master@{#400941}

[rhogan, 2016-06-20 18:47:40]

robhogan@gmail.com changed reviewers:
+ eae@chromium.org

[rhogan, 2016-06-20 18:47:41]

When a table has more than one section, layoutRows() needs to have an
up-to-date logicalTop() for the section. Otherwise it will calculate
the wrong offset from the top of the page for the row when figuring out whether
to put a strut on it.

[rhogan, 2016-06-20 18:47:59]

Description was changed from

==========
Handle pagination breaking on rows correctly when a table has >1 section

BUG=621359
==========

to

==========
Handle pagination breaking on rows correctly when a table has >1 section

When a table has more than one section, layoutRows() needs to have an
up-to-date logicalTop() for the section. Otherwise it will calculate
the wrong offset from the top of the page for the row when figuring out whether
to put a strut on it.

BUG=621359
==========

[eae, 2016-06-21 09:08:40]

LGTM

[eae, 2016-06-21 09:09:13]

The CQ bit was checked by eae@chromium.org

[commit-bot: I haz the power, 2016-06-21 09:09:52]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2076413002/60001

[commit-bot: I haz the power, 2016-06-21 10:26:44]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2016-06-21 10:29:27]

Description was changed from

==========
Handle pagination breaking on rows correctly when a table has >1 section

When a table has more than one section, layoutRows() needs to have an
up-to-date logicalTop() for the section. Otherwise it will calculate
the wrong offset from the top of the page for the row when figuring out whether
to put a strut on it.

BUG=621359
==========

to

==========
Handle pagination breaking on rows correctly when a table has >1 section

When a table has more than one section, layoutRows() needs to have an
up-to-date logicalTop() for the section. Otherwise it will calculate
the wrong offset from the top of the page for the row when figuring out whether
to put a strut on it.

BUG=621359

Committed: https://crrev.com/5aca76371f4c851adb4b1ac398ac45d62073967b
Cr-Commit-Position: refs/heads/master@{#400941}
==========

[commit-bot: I haz the power, 2016-06-21 10:29:28]

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