Bug 1467512 [wpt PR 11379] - Worker: Use Document's SettingsObject for top-level...

Bug 1467512 [wpt PR 11379] - Worker: Use Document's SettingsObject for top-level module script loading on dedicated workers, a=testonly

Automatic update from web-platform-testsWorker: Use Document's SettingsObject for top-level module script loading on dedicated workers

This CL makes Document serve its settings object ("outside settings") to
WorkerGlobalScope based on the following HTML spec:

  Step 13. "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

This SettingsObject is used as "fetch client settings object" for top-level
module script loading and static imports.

Before this CL, WorkerGlobalScope's settings object ("inside_settings_object")
is used as "fetch client settings object". This is obviously wrong and fails
some web-platform-tests. This change fixes them.

Change-Id: I87a78f38308e262425b848d99dc617dbddeb81e7
Bug: 842553, 845285
Reviewed-on: https://chromium-review.googlesource.com/1084133
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565199}

--

wpt-commits: ed2f4a4d980a609e817b4115d025cd06202a9882
wpt-pr: 11379