Evaluate worklet scripts as modules
Categories
(Core :: DOM: Core & HTML, enhancement, P3)
Tracking
()
People
(Reporter: karlt, Assigned: karlt)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
One thing that will likely fall into place with this work is that the Worklet.addModule() promise should only be rejected when "fetch a worklet script" (which includes ParseModule()) fails. Errors during "run a module script" should not cause the promise to be rejected (but do in current code because JS::Evaluate() is used to parse).
https://drafts.css-houdini.org/worklets/#fetch-and-invoke-a-worklet-script
https://github.com/w3c/css-houdini-drafts/issues/407 questions whether that is sane behavior.
Assignee | ||
Comment 2•5 years ago
|
||
The issue in comment 1 is getting in the way of writing tests for exception reporting, and so I'll address that with a simple module script implementation without import
support, and track implementation of fetching a complete module script graph in bug 1572644.
Assignee | ||
Comment 3•5 years ago
|
||
Assignee | ||
Comment 4•5 years ago
|
||
The separation of parse and evaluate steps permits implementation of behavior
on unhandled exception during evaluation that is different from that on
parsing error.
Depends on D41338
Assignee | ||
Comment 5•5 years ago
|
||
Updated•5 years ago
|
Comment 7•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/f532972750b5
https://hg.mozilla.org/mozilla-central/rev/e67d048b2d11
https://hg.mozilla.org/mozilla-central/rev/ba392537f7a9
Updated•5 years ago
|
Description
•