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

Unified Diff: third_party/WebKit/Source/core/dom/Document.h

Issue 2825343003: Clean compositing inputs for location APIs for sticky-affected elements. (Closed)
Patch Set: Rename EnsureLifecycleValidForLocationAPIsForNode Created 3 years, 8 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/dom/Document.h
diff --git a/third_party/WebKit/Source/core/dom/Document.h b/third_party/WebKit/Source/core/dom/Document.h
index 9b0ab6e6ced219e4f512f65ba15156b7e9a98393..51f61da7a717ae731a1e8e80e8b4a157c72c5374 100644
--- a/third_party/WebKit/Source/core/dom/Document.h
+++ b/third_party/WebKit/Source/core/dom/Document.h
@@ -513,6 +513,16 @@ class CORE_EXPORT Document : public ContainerNode,
PassRefPtr<ComputedStyle> StyleForElementIgnoringPendingStylesheets(Element*);
PassRefPtr<ComputedStyle> StyleForPage(int page_index);
+ // Ensures that location-based data will be valid for a given node.
+ //
+ // This will involve running style and layout if they are currently dirty, and
+ // it may also run compositing inputs as well if the node is in a sticky
+ // subtree (as the sticky offset may change the node's position).
+ //
+ // Due to this you should only call this if you definitely need valid location
+ // data, otherwise use one of the |UpdateStyleAndLayout...| methods above.
+ void EnsureAuxiliaryLocationDataValidForNode(const Node*);
+
// Returns true if page box (margin boxes and page borders) is visible.
bool IsPageBoxVisible(int page_index);

Powered by Google App Engine
This is Rietveld 408576698