[wpt-sync] Sync PR 52807 - Replace contentEncoding value in resourceTiming "unknown" with "@unknown"
Categories
(Core :: DOM: Performance APIs, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox141 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Attachments
(1 file)
Sync web-platform-tests PR 52807 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/52807
Details from upstream follow.
Guohui Deng <guohuideng@microsoft.com> wrote:
Replace contentEncoding value in resourceTiming "unknown" with "@unknown"
Per discussion in ietf and webperf WG folks, we don't reserve "unknown" value for the http parameter "content coding". Instead, we use a different value "@unknown" that cannot be registered as value of "content coding", to present a filtered value. The "@unknown" cannot be registered because it contains '@' that's prohibited.
Bug: 327941462
Change-Id: I61b681796a30d76880c9a4253f4095308ef1ab8bReviewed-on: https://chromium-review.googlesource.com/6506187
WPT-Export-Revision: be99b49c2fc1c85f4e88184ca26af8d71ae62ced
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
| Assignee | ||
Comment 2•1 year ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 1 tests and 29 subtests
Status Summary
Firefox
OK : 1
FAIL : 29
Chrome
OK : 1
PASS : 27
FAIL : 2
Safari
FAIL : 15
TIMEOUT: 2
NOTRUN : 13
Links
Details
New Tests That Don't Pass
- /resource-timing/content-encoding.https.html [wpt.fyi]
- contentEncoding in resource timing:
FAIL(Chrome:PASS, Safari:FAIL) - contentEncoding in resource timing 1:
FAIL(Chrome:PASS, Safari:FAIL) - contentEncoding in resource timing 2:
FAIL(Chrome:PASS, Safari:FAIL) - contentEncoding in resource timing 3:
FAIL(Chrome:PASS, Safari:FAIL) - contentEncoding in resource timing 4:
FAIL(Chrome:PASS, Safari:FAIL) - contentEncoding in resource timing 5:
FAIL(Chrome:PASS, Safari:FAIL) - contentEncoding in resource timing 6:
FAIL(Chrome:PASS, Safari:FAIL) - contentEncoding in resource timing 7:
FAIL(Chrome:PASS, Safari:FAIL) - contentEncoding in resource timing 8:
FAIL(Chrome:FAIL, Safari:FAIL) - contentEncoding in resource timing 9:
FAIL(Chrome:FAIL, Safari:FAIL) - contentEncoding in resource timing 10:
FAIL(Chrome:PASS, Safari:FAIL) - contentEncoding in resource timing 11:
FAIL(Chrome:PASS, Safari:FAIL) - contentEncoding in resource timing 12:
FAIL(Chrome:PASS, Safari:FAIL) - contentEncoding in resource timing 13:
FAIL(Chrome:PASS, Safari:FAIL) - contentEncoding in resource timing 14:
FAIL(Chrome:PASS, Safari:FAIL) - contentEncoding in resource timing 15:
FAIL(Chrome:PASS, Safari:TIMEOUT) - contentEncoding in resource timing 16:
FAIL(Chrome:PASS, Safari:NOTRUN) - contentEncoding in resource timing 17:
FAIL(Chrome:PASS, Safari:NOTRUN) - contentEncoding in resource timing 18:
FAIL(Chrome:PASS, Safari:NOTRUN) - contentEncoding in resource timing 19:
FAIL(Chrome:PASS, Safari:NOTRUN) - contentEncoding in resource timing 20:
FAIL(Chrome:PASS, Safari:NOTRUN) - contentEncoding in resource timing 21:
FAIL(Chrome:PASS, Safari:NOTRUN) - contentEncoding in resource timing 22:
FAIL(Chrome:PASS, Safari:NOTRUN) - contentEncoding in resource timing 23:
FAIL(Chrome:PASS, Safari:NOTRUN) - contentEncoding in resource timing 24:
FAIL(Chrome:PASS, Safari:NOTRUN) - contentEncoding in resource timing 25:
FAIL(Chrome:PASS, Safari:NOTRUN) - contentEncoding in resource timing 26:
FAIL(Chrome:PASS, Safari:NOTRUN) - contentEncoding in resource timing 27:
FAIL(Chrome:PASS, Safari:NOTRUN) - contentEncoding in resource timing 28:
FAIL(Chrome:PASS, Safari:NOTRUN)
- contentEncoding in resource timing:
| Assignee | ||
Comment 3•11 months ago
|
||
Automatic update from web-platform-tests
Replace contentEncoding value in resourceTiming "unknown" with "@unknown"
Per discussion in ietf and webperf WG folks, we don't reserve "unknown" value for the http parameter "content coding". Instead, we use a different value "@unknown" that cannot be registered as value of "content coding", to present a filtered value. The "@unknown" cannot be registered because it contains '@' that's prohibited.
Bug: 327941462
Change-Id: I61b681796a30d76880c9a4253f4095308ef1ab8b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6506187
Commit-Queue: Guohui Deng <guohuideng@microsoft.com>
Reviewed-by: Noam Rosenthal <nrosenthal@google.com>
Reviewed-by: Yoav Weiss (@Shopify) <yoavweiss@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1465956}
--
wpt-commits: 602789cf7bbe048f0e383cdbc2870766cc077749
wpt-pr: 52807
Comment 5•11 months ago
|
||
| bugherder | ||
Description
•