Bug 168009

Summary: An iframe without src attribute is never loaded inside the HTML parser
Product: WebKit Reporter: Ryosuke Niwa <rniwa>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, ap, bfulgham, cdumez
Priority: P2    
Version: Other   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Demo none

Ryosuke Niwa
Reported 2017-02-08 11:50:43 PST
<body> <div> <b id="b"><p><iframe id="f"></iframe><script> // p inside b triggers the adoption agency algorithm. alert(f.contentWindow); window.addEventListener('load', () => { alert(f.contentWindow); }) </script></b> Both of them say "undefined" but shouldn't. This is a major regression.
Attachments
Demo (224 bytes, text/html)
2017-02-08 11:53 PST, Ryosuke Niwa 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Ryosuke Niwa
Comment 1 2017-02-08 11:51:48 PST
Already regressed in r207475.
Ryosuke Niwa
Comment 2 2017-02-08 11:52:22 PST
Regressed in r203347.
Ryosuke Niwa
Comment 3 2017-02-08 11:53:09 PST
Will test further back in the history once I'm in the office.
Ryosuke Niwa
Comment 4 2017-02-08 11:53:37 PST
Created attachment 300933 [details] Demo
Ryosuke Niwa
Comment 5 2017-02-08 14:19:02 PST
Wow, this bug exists in Safari 9!
Ryosuke Niwa
Comment 6 2017-02-08 14:33:59 PST
Huh, maybe this never worked in Safari. I can even reproduce it in Safari 7.0.3
Ahmad Saleem
Comment 7 2022-05-30 11:26:00 PDT
This seems to be fixed in Safari 15.5 on macOS 12.4 and consistent with other browsers like Chrome Canary 104 and Firefox Nightly 102. Attached test case (demo) shows two dialog with [object Window] and then shows frame on the webpage for all browsers. Since this seems to be fixed and consistent across all browsers. It should be marked as "Resolved Fixed" or "Resolved Invalid". Thanks!
Alexey Proskuryakov
Comment 8 2022-05-31 10:00:14 PDT
Thank you for checking! We use "configuration changed" resolution when a bug goes away without a specific fix that we can point to.
Note You need to log in before you can comment on or make changes to this bug.