Closed Bug 1941991 Opened 1 month ago Closed 25 days ago

[wpt-sync] Sync PR 50115 - Expose contentEncoding in PerformanceResourceTiming

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox136 fixed)

RESOLVED FIXED
136 Branch
Tracking Status
firefox136 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 50115 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/50115
Details from upstream follow.

Guohui Deng <guohuideng@microsoft.com> wrote:

Expose contentEncoding in PerformanceResourceTiming

This CL introduce a contentEncoding field to Performance resource timing
object. This field is behind a feature flag.

PR to resource timing specification:
https://github.com/w3c/resource-timing/pull/411
PR to fetch specification:
https://github.com/whatwg/fetch/pull/1796

Bug: 327941462
Change-Id: I70cad190fe658fb3dbf8b401ff8393bc1d0782f0
Reviewed-on: https://chromium-review.googlesource.com/6098321
WPT-Export-Revision: d091a1e9970175b4c97aed83ad101d80a8ffc630

Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, and Chrome on GitHub CI

Total 2 tests and 25 subtests

Status Summary

Firefox

OK : 2
FAIL: 26

Chrome

OK : 2
FAIL: 26

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /navigation-timing/content-encoding.https.html?pipe=gzip [wpt.fyi]
    • contentEncoding should be gzip.: FAIL (Chrome: FAIL)
  • /resource-timing/content-encoding.https.html [wpt.fyi]
    • contentEncoding in resource timing: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 1: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 2: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 3: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 4: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 5: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 6: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 7: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 8: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 9: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 10: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 11: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 12: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 13: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 14: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 15: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 16: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 17: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 18: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 19: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 20: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 21: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 22: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 23: FAIL (Chrome: FAIL)
    • contentEncoding in resource timing 24: FAIL (Chrome: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/516f091d220e [wpt PR 50115] - Expose contentEncoding in PerformanceResourceTiming, a=testonly https://hg.mozilla.org/integration/autoland/rev/035daf11026d [wpt PR 50115] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 25 days ago
Resolution: --- → FIXED
Target Milestone: --- → 136 Branch
You need to log in before you can comment on or make changes to this bug.