Begin tracking why layout is invalidated

Source/core/dom/Element.cpp

Index: Source/core/dom/Element.cpp
diff --git a/Source/core/dom/Element.cpp b/Source/core/dom/Element.cpp
index 90680804180773222781633e4b86e7f32956d8d3..5dfcd1fc6da28f908bcf73e18c992e52aa4cf061 100644
--- a/Source/core/dom/Element.cpp
+++ b/Source/core/dom/Element.cpp
@@ -1605,7 +1605,7 @@ bool Element::pseudoStyleCacheIsInvalid(const ComputedStyle* currentStyle, Compu
                 // FIXME: We should do an actual diff to determine whether a repaint vs. layout
                 // is needed, but for now just assume a layout will be required. The diff code
                 // in LayoutObject::setStyle would need to be factored out so that it could be reused.
-                layoutObject()->setNeedsLayoutAndPrefWidthsRecalcAndFullPaintInvalidation();
+                layoutObject()->setNeedsLayoutAndPrefWidthsRecalcAndFullPaintInvalidation(LayoutInvalidationReason::StyleChange);
             }
             return true;
         }