Bug 272505
| Summary: | Inline module scripts should execute / signal errors in order | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Domenic Denicola <d> |
| Component: | WebCore JavaScript | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | annevk, cdumez, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Domenic Denicola
See test at https://github.com/web-platform-tests/wpt/pull/45660 and spec discussion at https://github.com/whatwg/html/pull/10272.
It appears WebKit delays running the script / firing the error event for a full task, instead of using microtask timing.
If you believe we should use task timing instead, please let me know and we can start a spec discussion.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Domenic Denicola
We've updated the spec
Domenic Denicola
(Sorry, I didn't realize that editing the title would submit my half-typed comment.)
We've updated the spec PR to align more with the WebKit / Chromium behavior, and use a full task instead.
The updated WPTs at https://github.com/web-platform-tests/wpt/pull/45660 show that WebKit behaves almost in line with the updated spec proposal. However, for some reason when performing this sequence of events:
- Insert a script with no parse error
- Insert a script with a parse error
WebKit seems to first fire the error event from script 2, then execute script 1.
Radar WebKit Bug Importer
<rdar://problem/126667873>