Bug 214357 - Always fire a load event for <embed> and <iframe> network errors
Summary: Always fire a load event for <embed> and <iframe> network errors
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Frames (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar, WPTImpact
Depends on:
Blocks:
 
Reported: 2020-07-15 09:22 PDT by Domenic Denicola
Modified: 2023-09-27 07:19 PDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Domenic Denicola 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.)
Comment 1 Radar WebKit Bug Importer 2020-07-16 17:56:51 PDT 
<rdar://problem/65699564>
Comment 3 jannis.rautenstrauch 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.