Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

<script type=webbundle>: Resolve a relative URL on the bundle's URL #31395

Merged
merged 1 commit into from
Oct 27, 2021

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Oct 27, 2021

The explainer PR is: WICG/webpackage#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:
WICG/webpackage#699 (comment)

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

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-3244822 branch 2 times, most recently from 5abdeae to 8fa669c Compare October 27, 2021 07:00
The explainer PR is: WICG/webpackage#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:
WICG/webpackage#699 (comment)

Bug: 1263807
Change-Id: Ic71f095589daa42db2d4649e2cf77212616b2f25
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3244822
Reviewed-by: Kunihiko Sakamoto <[email protected]>
Commit-Queue: Hayato Ito <[email protected]>
Cr-Commit-Position: refs/heads/main@{#935333}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants