Top-align table cells in rows that cross fragmentainer boundaries.

Top-align table cells in rows that cross fragmentainer boundaries.

Ignore whatever vertical-align says and force everything to be top aligned in
those cases. Edge also behaves like this.

Doing both fragmentation and vertical alignment for table parts could cause
unresolvable situations (cyclic dependencies).

Two tests that depended on vertical alignment working under such circumstances
are now invalid, and were therefore removed.

BUG=534751
Committed: https://crrev.com/c2025efb0537e16c304c37b1df4d687ec698cd68
Cr-Commit-Position: refs/heads/master@{#425112}

[mstensho (USE GERRIT), 2016-10-12 17:19:00]

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

[commit-bot: I haz the power, 2016-10-12 17:19:28]

Dry run: 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-10-12 18:51:25]

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

[commit-bot: I haz the power, 2016-10-12 18:51:26]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[mstensho (USE GERRIT), 2016-10-13 13:26:24]

Description was changed from

==========
Top-align table cells in rows that cross fragmentainer boundaries.

Ignore whatever vertical-align says and force everything to be top aligned in
those cases. Edge also behaves like this.

Doing both fragmentation and vertical alignment for table parts could cause
unresolvable situations (cyclic dependencies).

With this change, we no longer need the workaround that shrunk cells' height by
its first line's pagination strut (if any). In fact, it would be harmful to
keep it now.

Two tests that depended on vertical alignment working under such circumstances
are now invalid, and were therefore removed.

BUG=534751
==========

to

==========
Top-align table cells in rows that cross fragmentainer boundaries.

Ignore whatever vertical-align says and force everything to be top aligned in
those cases. Edge also behaves like this.

Doing both fragmentation and vertical alignment for table parts could cause
unresolvable situations (cyclic dependencies).

Two tests that depended on vertical alignment working under such circumstances
are now invalid, and were therefore removed.

BUG=534751
==========

[mstensho (USE GERRIT), 2016-10-13 13:29:25]

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

[commit-bot: I haz the power, 2016-10-13 13:29:43]

Dry run: 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-10-13 14:50:14]

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

[commit-bot: I haz the power, 2016-10-13 14:50:15]

Dry run: This issue passed the CQ dry run.

[mstensho (USE GERRIT), 2016-10-13 15:05:56]

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

[mstensho (USE GERRIT), 2016-10-13 15:05:58]

This is the first CL in a series of CLs whose aim is to make table layout
consistent and stable in fragmentation contexts, such as multicol and printing.

See https://bugs.chromium.org/p/chromium/issues/detail?id=534751#c9

[eae, 2016-10-13 17:32:28]

LGTM

[mstensho (USE GERRIT), 2016-10-13 18:47:09]

The CQ bit was checked by mstensho@opera.com

[commit-bot: I haz the power, 2016-10-13 18:47:45]

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-10-13 18:56:33]

Description was changed from

==========
Top-align table cells in rows that cross fragmentainer boundaries.

Ignore whatever vertical-align says and force everything to be top aligned in
those cases. Edge also behaves like this.

Doing both fragmentation and vertical alignment for table parts could cause
unresolvable situations (cyclic dependencies).

Two tests that depended on vertical alignment working under such circumstances
are now invalid, and were therefore removed.

BUG=534751
==========

to

==========
Top-align table cells in rows that cross fragmentainer boundaries.

Ignore whatever vertical-align says and force everything to be top aligned in
those cases. Edge also behaves like this.

Doing both fragmentation and vertical alignment for table parts could cause
unresolvable situations (cyclic dependencies).

Two tests that depended on vertical alignment working under such circumstances
are now invalid, and were therefore removed.

BUG=534751
==========

[commit-bot: I haz the power, 2016-10-13 18:56:34]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-10-13 18:58:45]

Description was changed from

==========
Top-align table cells in rows that cross fragmentainer boundaries.

Ignore whatever vertical-align says and force everything to be top aligned in
those cases. Edge also behaves like this.

Doing both fragmentation and vertical alignment for table parts could cause
unresolvable situations (cyclic dependencies).

Two tests that depended on vertical alignment working under such circumstances
are now invalid, and were therefore removed.

BUG=534751
==========

to

==========
Top-align table cells in rows that cross fragmentainer boundaries.

Ignore whatever vertical-align says and force everything to be top aligned in
those cases. Edge also behaves like this.

Doing both fragmentation and vertical alignment for table parts could cause
unresolvable situations (cyclic dependencies).

Two tests that depended on vertical alignment working under such circumstances
are now invalid, and were therefore removed.

BUG=534751

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

[commit-bot: I haz the power, 2016-10-13 18:58:46]

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