Closed Bug 1776899 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 34628 - Add render blocking status to Performance Resource Timing

Categories

(Core :: Performance: General, task, P4)

Product:
Core
Component:
Performance: General
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
104 Branch
Tracking Flags:
Tracking Status
firefox104 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Abin K Paul <abin.paul1@gmail.com> wrote:

Add render blocking status to Performance Resource Timing

This CL introduces a renderBlockingStatus field to Performance Resource
Timing object. This field is behind a Runtime Enabled Flag.

Bug:1337256
Change-Id: I0175fb0bce5e3e2aa8eeebd8cff3d2c9f920e3db
Reviewed-on: https://chromium-review.googlesource.com/3709521
WPT-Export-Revision: d352842aad3552e76a8de23ba4fdaf77a2a1b046

Component: web-platform-tests → Performance
Product: Testing → Core

CI Results

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

Total 8 tests and 1 subtests

Status Summary

Firefox

OK : 7
PASS : 12
FAIL : 3
TIMEOUT: 1
ERROR : 1
NOTRUN : 7

Chrome

OK : 7
PASS : 20
FAIL : 3
ERROR : 1

Safari

OK : 6
PASS : 2
FAIL : 10
TIMEOUT: 3
ERROR : 1
NOTRUN : 9

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /resource-timing/iframe-failed-commit.html [wpt.fyi]: ERROR (Chrome: ERROR, Safari: ERROR)
    • Test iframe from non-existent host gets reported: TIMEOUT (Chrome: PASS, Safari: TIMEOUT)
    • Test iframe redirecting to non-existent host gets reported: NOTRUN (Chrome: PASS, Safari: NOTRUN)
    • Same-origin iframe that complies with CSP attribute gets reported: NOTRUN (Chrome: PASS, Safari: NOTRUN)
    • Same-origin iframe that doesn't comply with CSP attribute gets reported: NOTRUN (Chrome: PASS, Safari: NOTRUN)
    • Cross-origin iframe that complies with CSP attribute gets reported: NOTRUN (Chrome: PASS, Safari: NOTRUN)
    • Cross-origin iframe that doesn't comply with CSP attribute gets reported: NOTRUN (Chrome: PASS, Safari: NOTRUN)
    • Same-origin empty iframe with a 200 status gets reported: NOTRUN (Chrome: PASS, Safari: NOTRUN)
    • Cross-origin empty iframe with a 200 status gets reported: NOTRUN (Chrome: PASS, Safari: NOTRUN)
  • /resource-timing/render-blocking-status-link.html [wpt.fyi]
    • Validate render blocking status of link resources in PerformanceResourceTiming: FAIL (Chrome: FAIL, Safari: FAIL)
  • /resource-timing/render-blocking-status-script.html [wpt.fyi]
    • Validate render blocking status of script resources in PerformanceResourceTiming: FAIL (Chrome: FAIL, Safari: FAIL)
  • /resource-timing/tojson.html [wpt.fyi]
    • Test toJSON() in PerformanceResourceTiming: FAIL (Chrome: FAIL, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8262b5e5ce7a [wpt PR 34628] - Add render blocking status to Performance Resource Timing, a=testonly https://hg.mozilla.org/integration/autoland/rev/196b5ac78e89 [wpt PR 34628] - Update wpt metadata, a=testonly
Regressions: 1778780

https://hg.mozilla.org/mozilla-central/rev/8262b5e5ce7a
https://hg.mozilla.org/mozilla-central/rev/196b5ac78e89

Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox104: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 104 Branch
You need to log in before you can comment on or make changes to this bug.