Parent page gets mouse events from an iframe with src "chrome-extension://..."
Reported by
froma...@gmail.com,
Apr 15 2018
|
||||||||||
Issue description
UserAgent: 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. Open "about:blank" page and open dev console for this page
2. Run the snippet of the code (paste the snippet to the console and press Enter)
3. Mouseenter the content of the iframe.
In this snippet I'm using an Adblock image as a source for the iframe. If you don't have the Adblock you need to modify the snippet to load a content of any of yours extensions.
The problem doesn't occur if there is non-chrome-extension content.
The snippet:
----------------
var div = document.createElement('div');
div.style.cssText = 'width: 300px; height: 50px; background: red; position: absolute; top: 0; left:0';
div.onmouseenter = function(){alert('div mouseenter');}
document.body.appendChild(div);
var iframe = document.createElement('iframe');
iframe.src = "chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/icons/icon24.png";
iframe.style.cssText = 'margin-top: 150px; margin-left: 100px';
document.body.appendChild(iframe);
----------------
What is the expected behavior?
nothing
What went wrong?
Parent page gets mouse events.
Page generates an alert message (as if I mouseenter the div)
Did this work before? N/A
Chrome version: 65.0.3325.181 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
,
Apr 15 2018
Yes, it doesn't overlap and it's not needed to. Here is the screencast to clarify: https://www.useloom.com/share/ff039cb8bfdd4621a361a6317d5ff2b4
,
Apr 15 2018
Ok, in Canary the problem is not reproduced.
,
Apr 15 2018
,
Apr 16 2018
Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 14.04 using chrome reported version #65.0.3325.181 and latest canary #68.0.3397.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...!!
,
Apr 16 2018
,
Apr 16 2018
,
Apr 20 2018
,
Apr 26 2018
Ken, are we keeping this iframe in a separate process since it is an extension? Is that correct? I remember talking to you about sending events in similar scenarios. Does this ring any bell in OOPIF code?
,
Apr 26 2018
I am *not* able to repro this on Linux tip-of-tree. Yes, the separate iframe is on account of the extension.
,
Apr 26 2018
A few more observations. I tested on Mac. I failed to see the problem on M66. However, M67 does show the problem. But again M68 (latest Canary) doesn't show the problem. Reporter, would you please test this on the latest version of Chrome and see whether you see this issue or not?
,
Apr 27 2018
In the latest stable Chrome version (66.0.3359.139) on my Win7 I can't replicate the problem.
,
Apr 27 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
,
Apr 27 2018
As issue is not reproducible for reporter on latest stable as per comment#12 marking this issue as wont-fix. @Reporter: Please feel free to raise a new issue if issue is still seen. Thanks! |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by woxxom@gmail.com
, Apr 15 2018