NEW214357
Always fire a load event for <embed> and <iframe> network errors 
https://bugs.webkit.org/show_bug.cgi?id=214357
Summary Always fire a load event for <embed> and <iframe> network errors
Domenic Denicola
Reported 2020-07-15 09:22:33 PDT
See https://github.com/whatwg/html/pull/4247 and https://github.com/web-platform-tests/wpt/pull/24518. Currently WebKit fires a load event for X-Frame-Options induced network errors, but fires no load event for nonexistant-host induced network errors. The specs do not distinguish between multiple types of network errors. Chromium currently follows the spec (load event for all network errors), whereas Firefox has similar behavior to Safari. Both <embed> and <iframe> exhibit similar behavior here. (<object> is much less interoperable and so we haven't touched the spec for it.)
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2020-07-16 17:56:51 PDT
<rdar://problem/65699564>
jannis.rautenstrauch
Comment 3 2023-09-27 07:19:35 PDT
In addition to nonexistant-host, WebKit also does not fire load events for incorrect data URLs (decoding failed; Chromium does) and non-existing schemes (Chromium also does not fire a load event here). Not sure what the correct behavior according to the specs would be as no tests for these cases seem to exist.
Note You need to log in before you can comment on or make changes to this bug.