Iframes are "jumping" when an embedded <a href="#" /> is clicked
Reported by
tylerr...@gmail.com,
Jun 12 2018
|
|||||||
Issue descriptionChrome Version : 67.0.3396.87 (Official Build) (64-bit) URLs (if applicable) : (Contains IFRAME) https://midspike.com/content/MSOS/ (In IFRAME) https://midspike.com/Content/WeatherScript/v1/ Other browsers tested: Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: Unknown Firefox: OK v60.0.2 (known) Edge: FAIL (it has it's own special snowflake issues) Vivaldi: FAIL 1.14.1077.45 Opera: FAIL 53.0.2907.68 Prerequisites: (1) Iframe contains an <a> tag with href="#" (2) <a href="#"> must be clicked What steps will reproduce the problem? (1) go to https://midspike.com/content/MSOS/ (2) press sign in (dont worry... no user sign-in implemented yet) (3) double click the snowflake icon (dubbed "Weatherscript") on the desktop (on website) (4) Click any blue link in the "Index of documentation" section (5) Observe iframe jumping up 5px - 15px (idk what it is) (6) Rinse and repeat in order to fully observe What is the expected result? Nothing out of the ordinary What happens instead? IFRAME "jumps" upward Please provide any additional information below. Attach a screenshot if possible. Before and after are included in the screenshot (in their respective order)
,
Jun 13 2018
tylerr514@ Thanks for the issue. Tested this issue on Windows 10 and Mac OS 10.13.5 on the reported version 67.0.3396.87 and the latest Canary 69.0.3457.0 by following the steps given above. On clicking on the blue links in the above site, cannot observe jump of the iframes. Checked issue on enabling/disabling Strict Site Isolation and is not reproducible either. Attached is the screen cast for reference. Request you to check and confirm if anything is missed from our end in triaging the issue. Also request you to retry the issue on a new chrome profile without any flags/extensions and update the thread with the observations. Thanks..
,
Jun 13 2018
,
Jun 15 2018
Sorry for not being clear as to what I meant. But in your video it showed the iframe moving up around 5-10px. Btw I'm not talking about the scrolling (that is intentional). Pay close attention to the site contained in my window frame. Use Dev tools to confirm that the iframe is relocated after clicking on a link. Btw everything (of relevance) inside of the window frame (ie: not the titlebar), for that particular window, is an iframe
,
Jun 15 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
,
Jun 15 2018
Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 17.10 using chrome reported version #67.0.3396.87 and latest canary #69.0.3461.0. This is a non-regression issue as it is observed from M60 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Jun 15 2018
The reason is that, for some reason, the <div> that contains the iframe (.windowContent) has a scrollHeight that's larger than its offsetHeight. This means it's "scrollable" so when you try to scroll the fragments into view, it causes this div to scroll too (you can reset the jump with scrollTop=0). If you make the container overflow: visible (and another container higher up too) the issue goes away. It's strange though because the only thing the <div> contains that takes space is the iframe and that's the same size as the container div according to dev tools. I can't find why scrollHeight is ~6px larger than the iframe. Changing the line-height property seems to affect this but I can't get them to be equal. Unfortunately I couldn't boil this down to a minimized repro but someone from layout team should have a look.
,
Jun 18 2018
The iframe is display inline so vertical alignment comes into play, even if no other content is present. This is how inlines work in blink and is not always what one would expect. Changing the vertical-align, line height, font size, or overflow property avoids the problem.
,
Jun 20 2018
Thank you for the feedback. Was able to reproduce successful mitigations (changing the display value). I would also like to note that, even though it is considered aberent behavior from one's expectations, it should not be discarded as a caviate of blink behavior. I will leave this "issue" opened, in case if anyone has anymore to add to the discussion, or if the chromium team wishes to close it. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by viswa.karala@chromium.org
, Jun 13 2018