Issue metadata
Sign in to add a comment
|
Cannot interact with iframe hosting chrome extension after changing tabs and coming back
Reported by
marco....@neednudge.com,
Mar 19 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.33 Safari/537.36 Steps to reproduce the problem: 1. Side load the included test extension 2. Try interacting with the iframe (eg. right click and inspect) 3. Change to a different tab (or create a new tab) and go back to the tab with the extension open 4. Try interacting with the iframe again What is the expected behavior? Should be able to interact with the iframe after changing tabs and coming back What went wrong? Can no longer interact with the iframe after changing tabs and coming back. Neither right or left clicking any elements, selecting text, etc. This issue does get fixed if you resize the browser. Did this work before? N/A Chrome version: 66.0.3359.33 Channel: beta OS Version: 10.0 Flash Version: This issue does not happen on Version 65.0.3325.162 (Official Build) (64-bit) (Win10) I added a comment to https://bugs.chromium.org/p/chromium/issues/detail?id=755515 as I thought it might be related. Also, this issue seems to be mentioned on comment 28 on: https://bugs.chromium.org/p/chromium/issues/detail?id=788807
,
Mar 20 2018
Able to reproduce this issue on reported version 66.0.3359.33 but issue got fixed on latest canary 67.0.3375.0 using Windows 10. Issue is not seen in Linux and Mac. Issue is observed only on enabling site Isolation flag from chrome://flags Tested with below steps: 1. Enabled site isolation flag >> Added attached extension 2. Right clicked, observed context menu 3. Navigated to other page, came back to example.com page and again rightclicked -- didn't observe context menu on clicking on it. Last Bad Build: 67.0.3372.0 First Good Build: 67.0.3373.0 CL: https://chromium.googlesource.com/chromium/src/+log/682206aafb5a1b9b3ae56099e2dc119311f3c3da..524c5cdd3d57ab87dc90a7d8842dd13921761a69 Probably fixed by https://chromium-review.googlesource.com/965016 from changelog. @samans: Please confirm the bug and help in merging it to M-66 if it is safe. Adding RB-Stable for M-66. Please remove if not the case. Thanks!
,
Mar 20 2018
It sounds plausible that my CL fixed this issue. I merged my CL into m66 yesterday, see https://chromium-review.googlesource.com/c/chromium/src/+/969181. Hopefully it makes it into the next beta release and we can verify the fix.
,
Mar 20 2018
Thanks all for handling this so quickly! I've also tested our main extension where this was originally found and confirmed that the issue has been fixed on 67.0.3376.1. Will keep tracking the issue to verify on the next beta release as well.
,
Mar 20 2018
Great! I'll mark it fixed. Thanks samans@!
,
Mar 20 2018
[Auto-generated comment by a script] We noticed that this issue is targeted for M-66; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-66 label, otherwise remove Merge-TBD label. Thanks.
,
Mar 20 2018
Re: comment 6: The fix was already merged to M66 in issue 822442 . |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Mar 20 2018