Automatic update from web-platform-testsWorker: Add referrer tests for ES Modules on dedicated workers
Referrer handling spans multiple algorithms in multiple specs, so I leave only
the entry points of them.
For top-level module script loading and static imports, referrer is determined
based on the "outside settings":
"Fetch a module worker script graph given url, outside settings, destination,
the value of the credentials member of options, and inside settings."
https://html.spec.whatwg.org/multipage/workers.html#worker-processing-model
For dynamic imports, referrer is determined based on the "referencing script's
settings object". In this case, it's "inside settings":
Step 2.4: "Fetch a module script graph given url, referencing script's settings object,
"script", and options. Wait until the algorithm asynchronously completes with
result."
https://html.spec.whatwg.org/multipage/webappapis.html#hostimportmoduledynamically(referencingscriptormodule,-specifier,-promisecapability)
These tests are still failing. Subsequent CLs will fix them.
Bug: 842553
Change-Id: I3855b91c7e6ba93f5c99fb63b24b6274e6b43211
Reviewed-on: https://chromium-review.googlesource.com/1088339
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564811}
--
wpt-commits: 4b4c626fc8602d1d06680a7d298789708fae5cd3
wpt-pr: 11369
An explanation of the Mozilla Source Code Directory Structure and links to
project pages with documentation can be found at:
https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure
For information on how to build Mozilla from the source code, see:
https://developer.mozilla.org/en/docs/Build_Documentation
To have your bug fix / feature added to Mozilla, you should create a patch and
submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at:
https://developer.mozilla.org/en/docs/Creating_a_patch
https://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree
If you have a question about developing Mozilla, and can't find the solution
on https://developer.mozilla.org, you can try asking your question in a
mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups
are accessible on Google Groups, or news.mozilla.org with a NNTP reader.]
You can download nightly development builds from the Mozilla FTP server.
Keep in mind that nightly builds, which are used by Mozilla developers for
testing, may be buggy. Firefox nightlies, for example, can be found at:
https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/
- or -
https://www.mozilla.org/firefox/channel/desktop/#nightly