Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(712)

Unified Diff: third_party/WebKit/Source/core/layout/LayoutBox.cpp

Issue 2473433002: Don't always have to relayout a child when fragmentainer height is unknown. (Closed)
Patch Set: Created 4 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: third_party/WebKit/Source/core/layout/LayoutBox.cpp
diff --git a/third_party/WebKit/Source/core/layout/LayoutBox.cpp b/third_party/WebKit/Source/core/layout/LayoutBox.cpp
index 5aad7f755841285c46b4aeb9ace8980f0c7075c0..76ef83016c55f1928b4f1a5be12b937b5fef57ba 100644
--- a/third_party/WebKit/Source/core/layout/LayoutBox.cpp
+++ b/third_party/WebKit/Source/core/layout/LayoutBox.cpp
@@ -4742,7 +4742,9 @@ bool LayoutBox::childNeedsRelayoutForPagination(const LayoutBox& child) const {
// have to. So we need to relayout.
return true;
}
- } else {
+ } else if (child.offsetToNextPage()) {
+ // This child did previously break, but it won't anymore, because we no
+ // longer have a known fragmentainer height.
return true;
}
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698