Use <script> tag, instead of <link> tag #670

hayatoito · 2021-08-31T03:28:37Z

This is a tracker to replace <link> tag with <script> tag in subresource loading.

Our action items would be:

Define a syntax such as:

<script type=webbundle>
    {
        "source": "foo.wbn",
        "scopes": ["js"],
        "resources": ["css/a.css", "css/b.css"]
    }
</script>

The syntax (json's scheme) should be compatible to a syntax used in BundlePreloading. We don't want to have two kinds of <script type=> elements for a webbundle.

Consider the semantic difference between <link> elements and <script> elements, and re-consider the features which can be supported in <script> tag. <script> tag can have more restrictions.

Chromium is starting to prototype to use <script> tag here (CL).
We'll share our feedback in this thread once we have more insights using <script> tag via prototyping.

This issue is one of the blockers to ship MVP, tracked in #648.

The text was updated successfully, but these errors were encountered:

Update the explainer so that it uses <script>-based API, instead of <link>-based API. Note: - The syntax is still tentative. We should align the syntax with ResourceBundles (issue WICG#670). - There are still some gaps between <link>-based API and <script>-based API. e.g. Request's mode and credentials mode. They should be resolved later.

* Switch to <script>-based API (issue #670) Update the explainer so that it uses <script>-based API, instead of <link>-based API. Note: - The syntax is still tentative. We should align the syntax with ResourceBundles (issue #670). - There are still some gaps between <link>-based API and <script>-based API. e.g. Request's mode and credentials mode. They should be resolved later.

hayatoito · 2021-09-16T02:26:08Z

FYI. We are starting to update the explainer. 725c28c

There are still remaining issues for <script>-based API. Let's use this issue for further discussion.

Introduce <script>-based API for subresource loading with Web Bundles. See the design doc [1] for the motivation of switching from <link>-based API to <script>-based API. The explainer [2] was already updated to use <script>-based API. This feature is guarded by `SubresourceWebBundles` flag. We eventually drop the <link rel=webbundle> support and remove the <link>-based API code once we can confirm <script>-based API can be used as a replacement of <link>-based API. This CL should be considered as the first step to switch to <script>-based API. There are still gaps between <link>-based API and <script>-based API, which will be addressed later [3]. This CL intentionally adds a very minimum test for <script type=webbundle>. Tests will be added in follow-up CLs. The plan is: 1. We will convert the existing tests incrementally, replacing <link>-based API with new <script>-based API. For example, for WPT, we will convert: from: wpt/web-bundle/subresource-loading/link-*.html to: wpt/web-bundle/subresource-loading/script-.html 2. If we find an issue of the implementation or find a missing feature by rewriting a test, we'll fix or update our implementation. 3. Continue until we can convert all existing tests. 4. Once we finish converting all tests, we can switch to <script>-based API and be ready to drop <link>-based API. We'll also add tests which are specific to <script>-based API as necessary. These efforts should be tracked by crbug.com/1245166. [1]: https://docs.google.com/document/d/1q_SodTcLuwya4cXt1gIRaVrkiaBfwWyPvkY1fqRKkgM/edit?usp=sharing&resourcekey=0-dqrFOGVCYsg8WRZ4RFgwuw [2]: https://github.com/WICG/webpackage/blob/main/explainers/subresource-loading.md [3]: WICG/webpackage#670 Bug: 1245166 Change-Id: I5109b6e692baf10fd1d8a31a31d93176d4dc4ad2

uasan · 2021-09-24T20:19:10Z

Does this mean that the download of the bundle will start no earlier than the parsing of the HTML document, and It is impossible to use HTTP preload link headers with a description of the bundle?

hayatoito · 2021-09-27T01:17:30Z

That's true. That's a cons of using <script>-based API, which is no longer able to support HTTP Header link automatically.

Introduce <script>-based API for subresource loading with Web Bundles. See the design doc [1] for the motivation of switching from <link>-based API to <script>-based API. The explainer [2] was already updated to use <script>-based API. This feature is guarded by `SubresourceWebBundles` flag. We eventually drop the <link rel=webbundle> support and remove the <link>-based API code once we can confirm <script>-based API can be used as a replacement of <link>-based API. This CL should be considered as the first step to switch to <script>-based API. There are still gaps between <link>-based API and <script>-based API, which will be addressed later [3]. This CL intentionally adds a very minimum test for <script type=webbundle>. Tests will be added in follow-up CLs. The plan is: 1. We will convert the existing tests incrementally, replacing <link>-based API with new <script>-based API. For example, for WPT, we will convert: from: wpt/web-bundle/subresource-loading/link-*.html to: wpt/web-bundle/subresource-loading/script-.html 2. If we find an issue of the implementation or find a missing feature by rewriting a test, we'll fix or update our implementation. 3. Continue until we can convert all existing tests. 4. Once we finish converting all tests, we can switch to <script>-based API and be ready to drop <link>-based API. We'll also add tests which are specific to <script>-based API as necessary. These efforts should be tracked by crbug.com/1245166. [1]: https://docs.google.com/document/d/1q_SodTcLuwya4cXt1gIRaVrkiaBfwWyPvkY1fqRKkgM/edit?usp=sharing&resourcekey=0-dqrFOGVCYsg8WRZ4RFgwuw [2]: https://github.com/WICG/webpackage/blob/main/explainers/subresource-loading.md [3]: WICG/webpackage#670 Bug: 1245166 Change-Id: I5109b6e692baf10fd1d8a31a31d93176d4dc4ad2

Introduce <script>-based API for subresource loading with Web Bundles. See the design doc [1] for the motivation of switching from <link>-based API to <script>-based API. The explainer [2] was already updated to use <script>-based API. This feature is guarded by `SubresourceWebBundles` flag. We eventually drop the <link rel=webbundle> support and remove the <link>-based API code once we can confirm <script>-based API can be used as a replacement of <link>-based API. This CL should be considered as the first step to switch to <script>-based API. There are still gaps between <link>-based API and <script>-based API, which will be addressed later [3]. This CL intentionally adds a very minimum test for <script>-based API because there are already WPT tests for <script type=webbundle>. They all have been marked as [ SKIP ] in TestExpectations until now. Now some of them are passing after this CL. We'll make the remaining tests pass in follow-up CLs, and also add tests which are specific to <script>-based API as necessary. These efforts should be tracked by crbug.com/1245166. [1]: https://docs.google.com/document/d/1q_SodTcLuwya4cXt1gIRaVrkiaBfwWyPvkY1fqRKkgM/edit?usp=sharing&resourcekey=0-dqrFOGVCYsg8WRZ4RFgwuw [2]: https://github.com/WICG/webpackage/blob/main/explainers/subresource-loading.md [3]: WICG/webpackage#670 Bug: 1245166 Change-Id: I5109b6e692baf10fd1d8a31a31d93176d4dc4ad2

Introduce <script>-based API for subresource loading with Web Bundles. See the design doc [1] for the motivation of switching from <link>-based API to <script>-based API. The explainer [2] was already updated to use <script>-based API. This feature is guarded by `SubresourceWebBundles` flag. We eventually drop the <link rel=webbundle> support and remove the <link>-based API code once we can confirm <script>-based API can be used as a replacement of <link>-based API. This CL should be considered as the first step to switch to <script>-based API. There are still gaps between <link>-based API and <script>-based API, which will be addressed later [3]. This CL intentionally adds a very minimum test for <script>-based API because there are already WPT tests for <script type=webbundle>. They all have been marked as [ SKIP ] in TestExpectations until now. Now some of them are passing after this CL. We'll make the remaining tests pass in follow-up CLs, and also add tests which are specific to <script>-based API as necessary. These efforts should be tracked by crbug.com/1245166. [1]: https://docs.google.com/document/d/1q_SodTcLuwya4cXt1gIRaVrkiaBfwWyPvkY1fqRKkgM/edit?usp=sharing&resourcekey=0-dqrFOGVCYsg8WRZ4RFgwuw [2]: https://github.com/WICG/webpackage/blob/main/explainers/subresource-loading.md [3]: WICG/webpackage#670 Bug: 1245166 Change-Id: I5109b6e692baf10fd1d8a31a31d93176d4dc4ad2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3128843 Commit-Queue: Hayato Ito <hayato@chromium.org> Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/main@{#933346}

Introduce <script>-based API for subresource loading with Web Bundles. See the design doc [1] for the motivation of switching from <link>-based API to <script>-based API. The explainer [2] was already updated to use <script>-based API. This feature is guarded by `SubresourceWebBundles` flag. We eventually drop the <link rel=webbundle> support and remove the <link>-based API code once we can confirm <script>-based API can be used as a replacement of <link>-based API. This CL should be considered as the first step to switch to <script>-based API. There are still gaps between <link>-based API and <script>-based API, which will be addressed later [3]. This CL intentionally adds a very minimum test for <script>-based API because there are already WPT tests for <script type=webbundle>. They all have been marked as [ SKIP ] in TestExpectations until now. Now some of them are passing after this CL. We'll make the remaining tests pass in follow-up CLs, and also add tests which are specific to <script>-based API as necessary. These efforts should be tracked by crbug.com/1245166. [1]: https://docs.google.com/document/d/1q_SodTcLuwya4cXt1gIRaVrkiaBfwWyPvkY1fqRKkgM/edit?usp=sharing&resourcekey=0-dqrFOGVCYsg8WRZ4RFgwuw [2]: https://github.com/WICG/webpackage/blob/main/explainers/subresource-loading.md [3]: WICG/webpackage#670 Bug: 1245166 Change-Id: I5109b6e692baf10fd1d8a31a31d93176d4dc4ad2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3128843 Commit-Queue: Hayato Ito <hayato@chromium.org> Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/main@{#933346}

issue WICG#670.

… event (#696) * Clarify that <script type=webbundle> doesn't fire a load event issue #670. * Mention an error event and issue #697

…tonly Automatic update from web-platform-tests Introduce <script type=webbundle> Introduce <script>-based API for subresource loading with Web Bundles. See the design doc [1] for the motivation of switching from <link>-based API to <script>-based API. The explainer [2] was already updated to use <script>-based API. This feature is guarded by `SubresourceWebBundles` flag. We eventually drop the <link rel=webbundle> support and remove the <link>-based API code once we can confirm <script>-based API can be used as a replacement of <link>-based API. This CL should be considered as the first step to switch to <script>-based API. There are still gaps between <link>-based API and <script>-based API, which will be addressed later [3]. This CL intentionally adds a very minimum test for <script>-based API because there are already WPT tests for <script type=webbundle>. They all have been marked as [ SKIP ] in TestExpectations until now. Now some of them are passing after this CL. We'll make the remaining tests pass in follow-up CLs, and also add tests which are specific to <script>-based API as necessary. These efforts should be tracked by crbug.com/1245166. [1]: https://docs.google.com/document/d/1q_SodTcLuwya4cXt1gIRaVrkiaBfwWyPvkY1fqRKkgM/edit?usp=sharing&resourcekey=0-dqrFOGVCYsg8WRZ4RFgwuw [2]: https://github.com/WICG/webpackage/blob/main/explainers/subresource-loading.md [3]: WICG/webpackage#670 Bug: 1245166 Change-Id: I5109b6e692baf10fd1d8a31a31d93176d4dc4ad2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3128843 Commit-Queue: Hayato Ito <hayato@chromium.org> Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/main@{#933346} -- wpt-commits: 47f30fc8a3227fb565186608e078451040de69c3 wpt-pr: 30816

…tonly Automatic update from web-platform-tests Introduce <script type=webbundle> Introduce <script>-based API for subresource loading with Web Bundles. See the design doc [1] for the motivation of switching from <link>-based API to <script>-based API. The explainer [2] was already updated to use <script>-based API. This feature is guarded by `SubresourceWebBundles` flag. We eventually drop the <link rel=webbundle> support and remove the <link>-based API code once we can confirm <script>-based API can be used as a replacement of <link>-based API. This CL should be considered as the first step to switch to <script>-based API. There are still gaps between <link>-based API and <script>-based API, which will be addressed later [3]. This CL intentionally adds a very minimum test for <script>-based API because there are already WPT tests for <script type=webbundle>. They all have been marked as [ SKIP ] in TestExpectations until now. Now some of them are passing after this CL. We'll make the remaining tests pass in follow-up CLs, and also add tests which are specific to <script>-based API as necessary. These efforts should be tracked by crbug.com/1245166. [1]: https://docs.google.com/document/d/1q_SodTcLuwya4cXt1gIRaVrkiaBfwWyPvkY1fqRKkgM/edit?usp=sharing&resourcekey=0-dqrFOGVCYsg8WRZ4RFgwuw [2]: https://github.com/WICG/webpackage/blob/main/explainers/subresource-loading.md [3]: WICG/webpackage#670 Bug: 1245166 Change-Id: I5109b6e692baf10fd1d8a31a31d93176d4dc4ad2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3128843 Commit-Queue: Hayato Ito <hayato@chromium.org> Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/main@{#933346} -- wpt-commits: 47f30fc8a3227fb565186608e078451040de69c3 wpt-pr: 30816

Use <script>-based API in the extension #670

@hayatoito

SHA: 6b36080 Reason: push, by @hayatoito Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Introduce <script>-based API for subresource loading with Web Bundles. See the design doc [1] for the motivation of switching from <link>-based API to <script>-based API. The explainer [2] was already updated to use <script>-based API. This feature is guarded by `SubresourceWebBundles` flag. We eventually drop the <link rel=webbundle> support and remove the <link>-based API code once we can confirm <script>-based API can be used as a replacement of <link>-based API. This CL should be considered as the first step to switch to <script>-based API. There are still gaps between <link>-based API and <script>-based API, which will be addressed later [3]. This CL intentionally adds a very minimum test for <script>-based API because there are already WPT tests for <script type=webbundle>. They all have been marked as [ SKIP ] in TestExpectations until now. Now some of them are passing after this CL. We'll make the remaining tests pass in follow-up CLs, and also add tests which are specific to <script>-based API as necessary. These efforts should be tracked by crbug.com/1245166. [1]: https://docs.google.com/document/d/1q_SodTcLuwya4cXt1gIRaVrkiaBfwWyPvkY1fqRKkgM/edit?usp=sharing&resourcekey=0-dqrFOGVCYsg8WRZ4RFgwuw [2]: https://github.com/WICG/webpackage/blob/main/explainers/subresource-loading.md [3]: WICG/webpackage#670 Bug: 1245166 Change-Id: I5109b6e692baf10fd1d8a31a31d93176d4dc4ad2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3128843 Commit-Queue: Hayato Ito <hayato@chromium.org> Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/main@{#933346}

hayatoito · 2022-09-27T08:18:23Z

[Issue Triage]
It seems we can close this issue. The spec is now using <script> tag.

Introduce <script>-based API for subresource loading with Web Bundles. See the design doc [1] for the motivation of switching from <link>-based API to <script>-based API. The explainer [2] was already updated to use <script>-based API. This feature is guarded by `SubresourceWebBundles` flag. We eventually drop the <link rel=webbundle> support and remove the <link>-based API code once we can confirm <script>-based API can be used as a replacement of <link>-based API. This CL should be considered as the first step to switch to <script>-based API. There are still gaps between <link>-based API and <script>-based API, which will be addressed later [3]. This CL intentionally adds a very minimum test for <script>-based API because there are already WPT tests for <script type=webbundle>. They all have been marked as [ SKIP ] in TestExpectations until now. Now some of them are passing after this CL. We'll make the remaining tests pass in follow-up CLs, and also add tests which are specific to <script>-based API as necessary. These efforts should be tracked by crbug.com/1245166. [1]: https://docs.google.com/document/d/1q_SodTcLuwya4cXt1gIRaVrkiaBfwWyPvkY1fqRKkgM/edit?usp=sharing&resourcekey=0-dqrFOGVCYsg8WRZ4RFgwuw [2]: https://github.com/WICG/webpackage/blob/main/explainers/subresource-loading.md [3]: WICG/webpackage#670 Bug: 1245166 Change-Id: I5109b6e692baf10fd1d8a31a31d93176d4dc4ad2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3128843 Commit-Queue: Hayato Ito <hayato@chromium.org> Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/main@{#933346} NOKEYCHECK=True GitOrigin-RevId: e1adbaeb278ee2ca83bc94a593cdc24dc660cda4

hayatoito mentioned this issue Aug 31, 2021

[Meta] A long term plan for subresource loading #648

Open

19 tasks

hayatoito added the subresource-loading label Aug 31, 2021

hayatoito mentioned this issue Sep 15, 2021

Switch to <script>-based API (issue #670) #679

Merged

hayatoito added a commit to hayatoito/webpackage that referenced this issue Sep 15, 2021

fixup! Switch to <script>-based API (issue WICG#670)

57f1f5f

hayatoito added a commit to hayatoito/webpackage that referenced this issue Sep 16, 2021

fixup! Switch to <script>-based API (issue WICG#670)

2c94c60

hayatoito mentioned this issue Sep 16, 2021

Consider dropping declarative scope for subresource loading. #580

Closed

chromium-wpt-export-bot mentioned this issue Sep 16, 2021

Introduce <script type=webbundle> web-platform-tests/wpt#30816

Merged

hayatoito added a commit to hayatoito/webpackage that referenced this issue Oct 25, 2021

Clarify that <sccript type=webbundle> doesn't fire a load event

6da74cb

issue WICG#670.

hayatoito added a commit to hayatoito/webpackage that referenced this issue Oct 25, 2021

Clarify that <script type=webbundle> doesn't fire a load event

3d4b2bf

issue WICG#670.

This was referenced Oct 25, 2021

Clarify that <script type=webbundle> doesn't fire a load nor an error event #696

Merged

<script type=webundle> should fire a load (or error) event? #697

Open

hayatoito added a commit that referenced this issue Oct 26, 2021

Clarify that <script type=webbundle> doesn't fire a load nor an error…

4096cd0

… event (#696) * Clarify that <script type=webbundle> doesn't fire a load event issue #670. * Mention an error event and issue #697

hayatoito mentioned this issue Oct 26, 2021

How to converge Subresource Loading with WebBundle APIs, <script type=webbundle>, with Bundle Preloading proposal #699

Closed

hayatoito added a commit to hayatoito/webpackage that referenced this issue Nov 8, 2021

Use <script>-based API in the extension WICG#670

2ffda32

hayatoito added a commit to hayatoito/webpackage that referenced this issue Nov 8, 2021

fixup! Use <script>-based API in the extension WICG#670

71ff9d3

hayatoito added a commit that referenced this issue Nov 8, 2021

Use <script>-based API in the extension #670 (#701)

6b36080

Use <script>-based API in the extension #670

github-actions bot added a commit that referenced this issue Nov 8, 2021

Use <script>-based API in the extension #670 (#701)

64f20b4

SHA: 6b36080 Reason: push, by @hayatoito Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

jeremyroman mentioned this issue Apr 21, 2022

Design Review: Speculation Rules (Prefetch) w3ctag/design-reviews#721

Closed

1 task

jeremyroman mentioned this issue Jun 3, 2022

Declarative <script> behavior whatwg/html#7986

Open

hayatoito closed this as completed Sep 27, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Use <script> tag, instead of <link> tag #670

Use <script> tag, instead of <link> tag #670

hayatoito commented Aug 31, 2021 •

edited

Loading

hayatoito commented Sep 16, 2021

uasan commented Sep 24, 2021 •

edited

Loading

hayatoito commented Sep 27, 2021

hayatoito commented Sep 27, 2022

Use <script> tag, instead of <link> tag #670

Use <script> tag, instead of <link> tag #670

Comments

hayatoito commented Aug 31, 2021 • edited Loading

hayatoito commented Sep 16, 2021

uasan commented Sep 24, 2021 • edited Loading

hayatoito commented Sep 27, 2021

hayatoito commented Sep 27, 2022

hayatoito commented Aug 31, 2021 •

edited

Loading

uasan commented Sep 24, 2021 •

edited

Loading