Issue metadata
Sign in to add a comment
|
OOPIF: sub iframe not getting mouse events (top-document-isolation)
Reported by
elad.ba...@overwolf.com,
Oct 17 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Example URL: content.overwolf.com/elad/iframe.html Steps to reproduce the problem: 1. enable chrome flag chrome://flags/#enable-top-document-isolation or run chrome with --top-document-isolation switch. 2. open content.overwolf.com/elad/iframe.html 3. try to press on the link, What is the expected behavior? the iframe src should response to events can't press on "Open the JavaScript Window Example 1" What went wrong? it seems like this issue related to the <div> next iframe, opening devtools and uncheck |background-image| property will make it work background-image: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACsAAAAWBAMAAACrl3iAAAAABlBMV…J9PGunad6yfqaMNim9Nljidm1w9kjsDS5LeG368y/TuPIHO Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? No Does this work in other browsers? N/A Chrome version: 61.0.3163.100 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 27.0 r0 the issue also happen if the <div> next the iframe has |background-color| property instead |background-image|.
,
Oct 18 2017
Able to reproduce this issue on reported version 61.0.3163.100 and on latest canary 64.0.3242.0 using Window10,Ubuntu 14.04 and Mac 10.12.6 with steps mentioned in comment#0. Manual Bisect Info: =============== Good Build: 59.0.3054.0 Bad Build: 59.0.3055.3 You are probably looking for a change made after 460176 (known good), but no later than 460177 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/34662d716488c15221573880f3462b1a3e2c123c..e2da63fad40fc329932c04030bca51f366ed721c Review-Url: https://codereview.chromium.org/2723963003 Suspecting same from changelog. @kenrb: Please confirm the bug and help in re-assigning if it is not related to your change. Thanks!
,
Oct 18 2017
This is a known issue with out-of-process iframes. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Oct 17 2017