Issue metadata
Sign in to add a comment
|
LayoutBox::offsetFromContainer(view()) is incorrect for fixed-position object |
||||||||||||||||||||||||
Issue descriptionLayoutBox::offsetFromContainer(view()) doesn't compensate view scroll offset for fixed-position object. This causes wrong result from LayoutBox::mapLocalToAncestor() for fixed-position objects if the ancestor is not a LayoutView.
,
Mar 29 2016
,
Mar 29 2016
Re #1: It affects paint invalidation of fixed-position objects, but I can workaround it.
,
Mar 30 2016
,
Apr 27 2016
Affected layout tests: compositing/repaint/fixed-pos-inside-composited-intermediate-layer.html compositing/overflow/fixed-scroll-in-empty-root-layer.html fast/repaint/fixed-under-composited-absolute-scrolled.html The tests are producing correct results because of a workaround of this bug in PaintInvalidationState. Will fix offsetFromContainer and remove the workaround.
,
Apr 27 2016
Still would like to pause this because it's still not clear in what coordinates (frame coordinates or LayoutView coordinates) that offsetFromContainer(view()) should return, until root-layer-scrolls launches. As there is no visible issue here (because of the workaround in PaintInvalidationState), will wait for root-layer-scrolls.
,
Oct 21 2016
Merge into bug 656172 which states the root cause and cover more cases. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by chrishtr@chromium.org
, Mar 29 2016