Chromium Code Reviews| Index: third_party/WebKit/Source/core/layout/compositing/CompositedLayerMapping.cpp |
| diff --git a/third_party/WebKit/Source/core/layout/compositing/CompositedLayerMapping.cpp b/third_party/WebKit/Source/core/layout/compositing/CompositedLayerMapping.cpp |
| index 5255bb300d90dc11ced663264acbfcd9eec11f6b..183a6638647cdc8bdb7c14d3886d193c595cc845 100644 |
| --- a/third_party/WebKit/Source/core/layout/compositing/CompositedLayerMapping.cpp |
| +++ b/third_party/WebKit/Source/core/layout/compositing/CompositedLayerMapping.cpp |
| @@ -2299,7 +2299,7 @@ IntRect CompositedLayerMapping::recomputeInterestRect(const GraphicsLayer* graph |
| FloatRect graphicsLayerBoundsInObjectSpace(graphicsLayerBounds); |
| graphicsLayerBoundsInObjectSpace.move(offsetFromAnchorLayoutObject); |
| // The object space means including writing mode flip. |
| - if (anchorLayoutObject->isBox()) |
| + if (anchorLayoutObject->isBox() && !anchorLayoutObject->isLayoutView()) |
|
chrishtr
2016/07/08 19:54:51
Why this change?
wkorman
2016/07/08 23:55:50
Good point, it looks like perhaps we can as you su
|
| toLayoutBox(anchorLayoutObject)->flipForWritingMode(graphicsLayerBoundsInObjectSpace); |
| // Now map the bounds to its visible content rect in screen space, including applying clips along the way. |