Issue metadata
Sign in to add a comment
|
Iframe scroll position lost if its visibility toggled
Reported by
suj...@zhservices.com,
Mar 27 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. Add ifarme with scroll in an html 2. Scroll it to the bottom 3. Change its style to display:hidden 4. make it visible 5. Now the iframes scroll resets to the top.Its previous scroll position is lost What is the expected behavior? The iframe must maintain its scroll position What went wrong? The scroll position of iframe is lost Did this work before? Yes 64 Does this work in other browsers? N/A Chrome version: 65.0.3325.181 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Mar 27 2018
Try running chrome with the following command line switch: --disable-blink-features=DisplayNoneIFrameCreatesNoLayoutObject If the bug is gone, the reason is r526112 which was fixed in issue 819189 (Chrome Canary 67).
,
Mar 28 2018
sujith@ Thanks for the issue. Request you to provide a sample file where this issue can be reproduced, which will help in further triaging. Also request you to retry the issue as per comment #2 and update the thread with the observations. Thanks..
,
Mar 28 2018
,
Mar 28 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 29 2018
sujith@ Thanks for the update. Able to reproduce this issue on Windows 10, Mac OS 10.12.6 and Ubuntu 14.04 on the latest Canary 67.0.3382.0 and Stable 65.0.3325.181 as per comment #4. Bisect Information: =================== Good Build: 62.0.3199.0 (Revision - 497962) Bad Build : 62.0.3199.0 (Revision - 498321) Unable to get the Changelog URL by executing the per-revision bisect script and Chromium bisect as all bad builds are invoked. Hence below is the manual Changelog URL from omahaproxy. https://chromium.googlesource.com/chromium/src/+log/62.0.3199.0..62.0.3200.0?pretty=fuller&n=10000 From the above Changelog, suspecting the below change: Reviewed-on: https://chromium-review.googlesource.com/627117 chaopeng@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner. Thanks.
,
Mar 30 2018
#6 range is wrong. #2 We can still reproduce this issue on latest build. And we can get correct scroll state if disable DisplayNoneIFrameCreatesNoLayoutObject. erikchen@ PTAL Thank you.
,
Mar 30 2018
I also build a test page: http://ht.chaopeng.me/frames.html
,
Mar 30 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Mar 27 2018Labels: Needs-Bisect Needs-Triage-M65