Bug 1737958 [wpt PR 31395] - <script type=webbundle>: Resolve a relative URL on the...

Bug 1737958 [wpt PR 31395] - <script type=webbundle>: Resolve a relative URL on the bundle's URL, a=testonly

Automatic update from web-platform-tests
<script type=webbundle>: Resolve a relative URL on the bundle's URL

The explainer PR is: https://github.com/WICG/webpackage/pull/700

One of the gaps between the Subresource Loading with WebBundles and
Bundle Preloading proposals is "how to resolve a relative URL of
resources". The former is using document's base URL, and the latter is
using the bundle's URL. We have to align.

At the era of <link>-based API, using a document's base URL might make
sense because `resources` are specified in the link element's
attribute.

Now we use <script>-based APIs, and `resources` is specified in JSON, so
we no longer have any strong reason to use a document's base URL.

See the spec discussion for details:
https://github.com/WICG/webpackage/issues/699#issuecomment-952472275

Bug: 1263807
Change-Id: Ic71f095589daa42db2d4649e2cf77212616b2f25
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3244822
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Commit-Queue: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/main@{#935333}

--

wpt-commits: 6bbec86c72b31033d100beb6c571c37f1cdc5446
wpt-pr: 31395