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

Issue 645726 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit 29 days ago
Closed: Oct 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Dynamic iframe source missing from devtools source tree when data posted into iframe using target

Reported by arnaud.k...@ybo.com.sg, Sep 10 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce the problem:
1. Dynamically create Iframe with document.createElement
2. Add iframe to document with document.body.appendChild
3. Use top window form to post parameters into iframe using iframe name as form target

What is the expected behavior?
(index) entry under the iframe tree structure of the devtools source tree

What went wrong?
(index) is missing

Did this work before? No 

Chrome version: 52.0.2743.116  Channel: stable
OS Version: Fedora 24
Flash Version: Shockwave Flash 22.0 r0

Under the console tab it shows the iframe list with (about:blank) added. Is this because the src attribute was never set?
 
An additional side effect is that exceptions caused by iframe javascript source are logged in the console with a stack trace having clickable references to source code lines of the top window instead of the iframe source. However, the stack trace object and function names are correct.
Could you help us with a reduced repro of this bug? just a small example, as we don't know how to perfectly recreate this situation.

Something on JSbin or https://plnkr.co would work well. Thanks!
Labels: Needs-Feedback

Comment 4 by alph@chromium.org, Oct 10 2016

Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Status: WontFix (was: Assigned)
Closing since the lack of feedback 

Sign in to add a comment