Chromium Code Reviews| Index: third_party/WebKit/Source/core/layout/LayoutTableRow.cpp |
| diff --git a/third_party/WebKit/Source/core/layout/LayoutTableRow.cpp b/third_party/WebKit/Source/core/layout/LayoutTableRow.cpp |
| index cc800331100f484e9f021dd638b8e549bd1c5241..ca0ccfc78959f63d941bcc48d45a440b2925eb43 100644 |
| --- a/third_party/WebKit/Source/core/layout/LayoutTableRow.cpp |
| +++ b/third_party/WebKit/Source/core/layout/LayoutTableRow.cpp |
| @@ -77,6 +77,7 @@ void LayoutTableRow::styleDidChange(StyleDifference diff, const ComputedStyle* o |
| if (table && !table->selfNeedsLayout() && !table->normalChildNeedsLayout() && oldStyle && oldStyle->border() != style()->border()) |
| table->invalidateCollapsedBorders(); |
| + // TODO(dgrogan): Do we need to setPreferredLogicalWidthsDirty even when !diff.needsFullLayout()? |
|
mstensho (USE GERRIT)
2016/05/25 12:18:28
No? :) See my other comment.
|
| if (table && oldStyle && diff.needsFullLayout() && needsLayout() && table->collapseBorders() && borderWidthChanged(oldStyle, style())) { |
| // If the border width changes on a row, we need to make sure the cells in the row know to lay out again. |
| // This only happens when borders are collapsed, since they end up affecting the border sides of the cell |