[css] Don't let table parts be layout boundaries

third_party/WebKit/Source/core/layout/LayoutObject.cpp

 /*
  * Copyright (C) 1999 Lars Knoll (knoll@kde.org)
  *           (C) 1999 Antti Koivisto (koivisto@kde.org)
  *           (C) 2000 Dirk Mueller (mueller@kde.org)
  *           (C) 2004 Allan Sandfeld Jensen (kde@carewolf.com)
  * Copyright (C) 2004, 2005, 2006, 2007, 2008, 2011 Apple Inc. All rights reserved.
  * Copyright (C) 2009 Google Inc. All rights reserved.
  * Copyright (C) 2009 Torch Mobile Inc. All rights reserved. (http://www.torchmobile.com/)
  *
  * This library is free software; you can redistribute it and/or
@@ skipping 695 matching lines @@
 
 static inline bool objectIsRelayoutBoundary(const LayoutObject* object)
 {
     // FIXME: In future it may be possible to broaden these conditions in order to improve performance.
     if (object->isTextControl())
         return true;
 
     if (object->isSVGRoot())
         return true;
 
+    // Table parts can't be relayout roots since the table is responsible for layouting all the parts.
+    if (object->isTablePart())
+        return false;
+
     if (object->style()->containsLayout() && object->style()->containsSize())
         return true;
 
     if (!object->hasOverflowClip())
         return false;
 
     if (object->style()->width().isIntrinsicOrAuto() || object->style()->height().isIntrinsicOrAuto() || object->style()->height().hasPercent())
         return false;
 
-    // Table parts can't be relayout roots since the table is responsible for layouting all the parts.
-    if (object->isTablePart())
-        return false;
-
     // Scrollbar parts can be removed during layout. Avoid the complexity of having to deal with that.
     if (object->isLayoutScrollbarPart())
         return false;
 
     // Inside multicol it's generally problematic to allow relayout roots. The multicol container
     // itself may be scheduled for relayout as well (due to other changes that may have happened
     // since the previous layout pass), which might affect the column heights, which may affect how
     // this object breaks across columns). Spanners may also have been added or removed since the
     // previous layout pass, which is just another way of affecting the column heights (and the
     // number of rows). Instead of identifying cases where it's safe to allow relayout roots, just
@@ skipping 2948 matching lines @@
         const blink::LayoutObject* root = object1;
         while (root->parent())
             root = root->parent();
         root->showLayoutTreeAndMark(object1, "*", object2, "-", 0);
     } else {
         fprintf(stderr, "Cannot showLayoutTree. Root is (nil)\n");
     }
 }
 
 #endif