7161 2006-02-09 11:30:32 -0800 <iframe src=""> load event is dispatched synchronously unlike Chrome Canary and Firefox 2023-08-18 11:33:37 -0700 1 1 1 Unclassified WebKit DOM 420+ Mac OS X 10.4 NEW BrowserCompat, HasReduction, InRadar P2 Normal --- 1 ap webkit-unassigned ahmad.saleem792 ap bfulgham cdumez ian rniwa techrazy.yang webkit-bug-importer oldest_to_newest 31957 0 ap 2006-02-09 11:30:32 -0800 See the attached test case (which works as expected in Firefox and WinIE). The document body has an element: <p id=console>FAILURE</p> For whatever reason, document.getElementById("console") returns null if called from an IFrame onload handler. 31958 1 6367 ap 2006-02-09 11:31:07 -0800 Created attachment 6367 test case 31960 2 ap 2006-02-09 11:45:19 -0800 Starts to work if the iframe is moved below <p>. "onclick handler" in the alert was supposed to be "onload handler", of course. It is there to indicate that the handler is called at all (didn't fire before, bug 3609). 1887837 3 ahmad.saleem792 2022-07-30 05:49:35 -0700 I am able to reproduce this bug in Safari 15.6 on macOS 12.5 using attached test case and Safari is only browser - which shows "FAILURE" while all other browsers return "SUCCESS" on this test case. I tested it in "Private Window" to avoid any cache issue as well. Just wanted to share updated test results. Thanks! 1887838 4 ahmad.saleem792 2022-07-30 05:50:04 -0700 Other browsers which show "SUCCESS" - Chrome Canary 106 and Firefox Nightly 105. Forgot to add them. 1887898 5 rniwa 2022-07-30 13:36:25 -0700 Ah, this is an issue of when load event is fired. Safari is loading iframe synchronously before p element has been inserted into the document. 1887901 6 webkit-bug-importer 2022-07-30 13:43:27 -0700 <rdar://problem/97844849> 1887931 7 rniwa 2022-07-31 01:01:31 -0700 Hm... Chrome stable (103.0.5060.134) also fails the test. I suppose Chrome changed its behavior very recently. 1887934 8 ahmad.saleem792 2022-07-31 02:18:20 -0700 So I just tested this in Chrome Beta (104.0.5112.65) and Chrome Dev (105.0.5195.10) and both also show "FAILURE" for this test case, so indeed, it is something which got fixed in Chrome just in Canary branch. I tried to also look for some such iframe related bugs and only came across following (This is just guess work - so ignore, if irrelevant): -> Fixed just 19 days ago: https://chromium.googlesource.com/chromium/src/+/cf2f72ac8431c836b7ecb92a87018ee7f3c2db64 1972111 9 ahmad.saleem792 2023-08-18 11:33:37 -0700 Is this code segment in question: https://searchfox.org/wubkat/source/Source/WebCore/loader/PolicyChecker.cpp#259 // We ignore the response from the client for initial empty document loads and proceed with the load synchronously. 6367 2006-02-09 11:31:07 -0800 2006-02-09 11:31:07 -0800 test case iframe-onload.html text/html 513 ap PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMDEgVHJhbnNpdGlvbmFs Ly9FTiIKICAgICAgICAiaHR0cDovL3d3dy53My5vcmcvVFIvaHRtbDQvbG9vc2UuZHRkIj4KPGh0 bWw+CjxoZWFkPgo8dGl0bGU+aWZyYW1lIG9ubG9hZCBoYW5kbGVyPC90aXRsZT4KPHNjcmlwdD4K CglmdW5jdGlvbiByZXBvcnRTdWNjZXNzKCkgewoJCWFsZXJ0KCJvbmNsaWNrIGhhbmRsZXIiKTsK CQlkb2N1bWVudC5nZXRFbGVtZW50QnlJZCgiY29uc29sZSIpLmZpcnN0Q2hpbGQubm9kZVZhbHVl ID0gIlNVQ0NFU1MiOwoJfQoJCjwvc2NyaXB0Pgo8L2hlYWQ+Cjxib2R5Pgo8aUZyYW1lIHN0eWxl PSJ3aWR0aDozNTBweDtib3JkZXI6ZG90dGVkIGdyZWVuIDFweCIgd2lkdGg9IjIwMCIgc3JjPSIi IGhlaWdodD0iMjAwIiBvbmxvYWQ9ImphdmFzY3JpcHQ6cmVwb3J0U3VjY2VzcygpIj5zb21lIGNv bnRlbnQ8L2lGcmFtZT4KPHAgaWQ9Y29uc29sZT5GQUlMVVJFPC9wPgo8L2JvZHk+CjwvaHRtbD4K