Bug 193512 - <link> load/error event should fire before pending parsing-blocking script is "unblocked"
Summary: <link> load/error event should fire before pending parsing-blocking script is...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: UI Events (show other bugs)
Version: Safari Technology Preview
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2019-01-16 15:16 PST by Dominic Farolino
Modified: 2019-01-17 14:23 PST (History)
6 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 Dominic Farolino 2019-01-16 15:16:57 PST 
As per the large https://github.com/whatwg/html/pull/4031, it is now well-specified that the load event should be fire before the Document's script-blocking style sheet counter [1] is decremented, and scripting is unblocked.

Currently Safari and Chrome fire load/error events sometime after the pending parsing-blocking script is run, which is confusing and now against the spec. Note: Firefox behaves correctly here. Also note: The task source for the <link> load/error events has changed from the DOM manipulation task source to the networking task source too.

WPTs for this are available at: https://github.com/web-platform-tests/wpt/pull/14899.

----

[1]: http://html.spec.whatwg.org/multipage/semantics.html#script-blocking-style-sheet-counter.
Comment 1 Radar WebKit Bug Importer 2019-01-17 14:23:43 PST 
<rdar://problem/47364258>