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_ng/builds/341766)
Dry run: Try jobs failed on following builders: linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/190621)
Description was changed from
==========
Margins that start at fragmentainer boundaries should be collapsed away.
This only applies if the fragmentainer break is unforced. If it's forced, the
margin is to be preserved.
See https://drafts.csswg.org/css-break/#break-margins
Get rid of LayoutBlock::nextPageLogicalTop(), since nobody calls it anymore.
BUG=440362
==========
to
==========
Margins that start at fragmentainer boundaries should be collapsed away.
This only applies if the fragmentainer break is unforced. If it's forced, the
margin is to be preserved.
See https://drafts.csswg.org/css-break/#break-margins
Get rid of LayoutBlock::nextPageLogicalTop(), since nobody calls it anymore.
BUG=440362
Committed: https://crrev.com/506506eac78a8106c4e92866a59b8c724ddc8b88
Cr-Commit-Position: refs/heads/master@{#435917}
==========
commit-bot: I haz the power
Patchset 4 (id:??) landed as https://crrev.com/506506eac78a8106c4e92866a59b8c724ddc8b88 Cr-Commit-Position: refs/heads/master@{#435917}
Issue 2542723002: Margins that start at fragmentainer boundaries should be collapsed away.
(Closed)
Created 4 years ago by mstensho (USE GERRIT)
Modified 4 years ago
Reviewers: eae
Base URL:
Comments: 0