New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 919020 link

Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue 878658
Owner:
Closed: Jan 15
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Event reference in limbo after an iframe reload

Reported by mah...@gmail.com, Jan 4

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce the problem:
1. Please view the following test page:
2. http://www.starlords3k.com/tests/iframe_click_lost_top.php
3. 

What is the expected behavior?
Elements should be able to reference functions in window.top

What went wrong?
On reload of the iframe references to a previously referenced function in window.top (or other iframes) no longer trigger. While calls to the same function work as expected.

Did this work before? Yes Pretty sure it worked in 70, works in Firefox

Chrome version: 71.0.3578.98  Channel: stable
OS Version: 10.0
Flash Version:
 
Link to cleaner test case: http://www.starlords3k.com/tests/chrome_919020_top.html
chrome_919020_file.html
849 bytes View Download
chrome_919020_top.html
1.4 KB View Download
If you load the iframe with some other file, then load chrome_919020_file.html into it again, the references still do not trigger!
Labels: Needs-Bisect Needs-Triage-M71
Bisected to r597054 = 1b2f95835607dbb9c6021df8893fb18f4c7aee9e = crrev.com/c/1215512 by yukiy@google.com
"Create new EventHandler and base class for EventListener/EventHandler"
Landed in 71.0.3572.0
Cc: yukiy@google.com susan.boorgula@chromium.org
Labels: -Pri-2 -Needs-Bisect RegressedIn-71 ReleaseBlock-Stable Triaged-ET Target-71 Target-72 Target-73 M-71 FoundIn-71 FoundIn-73 FoundIn-72 hasbisect OS-Linux OS-Mac Pri-1
Owner: haraken@chromium.org
Status: Assigned (was: Unconfirmed)
mahks1@ Thanks for the issue.

Able to reproduce this issue on Windows 10, Ubuntu 14.04 and Mac OS 10.13.6 on the latest Stable 71.0.3578.98 and latest Canary 73.0.3663.0.

Bisect Information:
====================
Good Build: 71.0.3571.0
Bad Build : 71.0.3572.0

As per comment #4, suspecting the below Change.
Reviewed-on: https://chromium-review.googlesource.com/c/1215512

As owner yukiy@ is not available, assigning the bug to reviewer haraken@.
haraken@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner.

Adding 'ReleaseBlock-Stable' for M-71 as this is a recent regression. Please feel free to remove if it is not applicable.

Thanks...
Components: -Blink Blink>Bindings
Labels: M-72
Friendly ping! Could you please provide any update on this issue as it has been marked as a stable blocker.

Thank You!
Cc: haraken@chromium.org
Owner: yukishiino@chromium.org
Ran into this today as well - some notes that might with debugging:

1) The onclick event still fires if you manually use javascript to do so (only the actual mouseclicks don't work)

2) This happens even if you move the element out of the iframe before reloading.

Attached some javascript you can run on the test site, http://www.starlords3k.com/tests/chrome_919020_top.html to demonstrate these things.

Hope it helps with debugging.
js_move_test_me.txt
363 bytes View Download
[bulk update] Just a heads up, M72 stable is about 2 weeks away. This issue is marked as RB-Stable. Please take a look. 
Labels: -ReleaseBlock-Stable OS-Android OS-Chrome
Mergedinto: 878658
Status: Duplicate (was: Assigned)
This is pretty hard to fix in M72 at this point, and considering that M71 has been having the same issue without an issue report by now, let me fix this issue in M73 and remove RBS.

Essentially  Issue 878658  is triggering this issue, I think.

Comment 13 by mah...@gmail.com, Jan 18 (4 days ago)

Did the fix to 878658 solve this?

Comment 14 by yukishiino@chromium.org, Jan 18 (4 days ago)

Yes, I locally confirmed the fix.
In a few days, you'll be able to confirm the fix on Canary channel.

Sign in to add a comment