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

Unified Diff: third_party/WebKit/Source/core/layout/LayoutBlock.h

Issue 2454083002: Need a deep layout pass when becoming (un)fragmented. (Closed)
Patch Set: Created 4 years, 2 months 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
Index: third_party/WebKit/Source/core/layout/LayoutBlock.h
diff --git a/third_party/WebKit/Source/core/layout/LayoutBlock.h b/third_party/WebKit/Source/core/layout/LayoutBlock.h
index 804954fe785c3c19de25958bdde63af399a34810..6058995f0636aa0ada54bb94a91b316d4f0c2cf9 100644
--- a/third_party/WebKit/Source/core/layout/LayoutBlock.h
+++ b/third_party/WebKit/Source/core/layout/LayoutBlock.h
@@ -545,6 +545,14 @@ class CORE_EXPORT LayoutBlock : public LayoutBox {
unsigned m_hasPositionedObjects : 1;
unsigned m_hasPercentHeightDescendants : 1;
+ // When an object ceases to establish a fragmentation context (e.g. the
+ // LayoutView when we're no longer printing), we need a deep layout
+ // afterwards, to clear all pagination struts. Likewise, when an object
+ // becomes fragmented, we need to re-lay out the entire subtree. There might
+ // be forced breaks somewhere in there that we suddenly have to pay attention
+ // to, for all we know.
+ unsigned m_paginationStateChanged : 1;
+
// FIXME: This is temporary as we move code that accesses block flow
// member variables out of LayoutBlock and into LayoutBlockFlow.
friend class LayoutBlockFlow;

Powered by Google App Engine
This is Rietveld 408576698