[ResourceTiming]: Update WPTs concerning opaque origins #29785
Merged
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
Jul 26, 2021
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-3042198
branch
from
388fb5c
to
1831c17
Compare
Both TAO-null-opaque-origin.html and TAO-case-insensitive-null-opaque-origin.sub.html test the Resource Timing API when resources are fetched from an opaque origin context. This change updates those tests to conform to wpt/resource-timing/CodingConventions.md. Bug: 1171767 Change-Id: I3bfbaa4a714a4582a5c900aa345df118828e1e0e GithubIssue: w3c/resource-timing#254 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3042198 Commit-Queue: Tom McKee <tommckee@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#905292}
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-3042198
branch
from
1831c17
to
49e3278
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.
Both TAO-null-opaque-origin.html and
TAO-case-insensitive-null-opaque-origin.sub.html test the Resource
Timing API when resources are fetched from an opaque origin context.
This change updates those tests to conform to
wpt/resource-timing/CodingConventions.md.
Bug: 1171767
Change-Id: I3bfbaa4a714a4582a5c900aa345df118828e1e0e
GithubIssue: w3c/resource-timing#254
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3042198
Commit-Queue: Tom McKee <tommckee@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#905292}