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

Issue 679203 link

Starred by 1 user
Status: Duplicate
Merged: issue 660496
Owner:
lfg@chromium.org
Closed: Jan 2017
Cc:
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

DevRel-SAP: Regression - iframe doesn't create a request after setting the src property

Reported by orit.ha...@sap.com, Jan 8 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
1. Open the attached file. 
2. Click on "Remove iframe" button.

What is the expected behavior?
After clicking on the button (step 2), the right iframe is removed. During the unload event of this iframe, the src property of the left iframe is set with a url. This iframe creates a request that calls the url to be rendered in the iframe.

What went wrong?
After clicking on the button (step 2), the right iframe is removed. During the unload event of this iframe, the src property of the left iframe is set with a url. This iframe doesn't create a request to call the url, therefore the url is not rendered in the iframe.

Did this work before? Yes chrome 53.0.2785.116

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0

Works fine with Firefox and Chrome 53.
iFrameTest1.html
1.4 KB View Download

Comment 1 by tkent@chromium.org, Jan 9 2017

Cc: lfg@chromium.org
Components: Blink>Loader
Labels: Needs-Bisect

Comment 2 by brajkumar@chromium.org, Jan 9 2017

Cc: -lfg@chromium.org brajkumar@chromium.org
Labels: -Needs-Bisect hasbisect-per-revision M-57 OS-Linux OS-Mac
Owner: lfg@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce this issue on Windows-10, Ubuntu 14.04 and Mac OS 10.12 using chrome latest stable M55-55.0.2883.87


Good build:54.0.2838.0
Bad build: 54.0.2840.0

Using the per-revision bisect providing the bisect results,

You are probably looking for a change made after 414587 (known good), but no later than 414588 (first known bad).

CHANGE-LOG URL:
---------------------------------------
https://chromium.googlesource.com/chromium/src/+log/134f2a8d2eb76219bb8d650970859116dfb1606e..8fb70277dba468aac9d2eae51e432d76667a79db

From the CL above, assigning the issue to the concern owner
Review-Url: https://codereview.chromium.org/2206843003

lfg@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

Comment 3 by lfg@chromium.org, Jan 9 2017

Mergedinto: 660496
Status: Duplicate (was: Assigned)
►

Sign in to add a comment