Add WPT about how CORS behaves in WebBundle subresource loading #27141
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wpt-pr-bot
approved these changes
Jan 12, 2021
It would be better to clarify an expected behavior how CORS behaves for WebBundle subresource loading in the current implementation. Note that - The expected behavior is a tentative decision, which might change in the future. The spec side issue is WICG/webpackage#609. - A |crossorigin| attribute is not supported yet. BUG=1149816 Change-Id: Ic104ec039a07f864b6a60452ff42f2ec09a03c2c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2617167 Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Hayato Ito <hayato@chromium.org> Cr-Commit-Position: refs/heads/master@{#842863}
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-2617167
branch
from
a04d3f8
to
3adab1a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It would be better to clarify an expected behavior how CORS behaves for
WebBundle subresource loading in the current implementation.
Note that
change in the future. The spec side issue is
Clarify how CORS behaves for Subresource Loading with WebBundles WICG/webpackage#609.
BUG=1149816
Change-Id: Ic104ec039a07f864b6a60452ff42f2ec09a03c2c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2617167
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Commit-Queue: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#842863}