Closed Bug 2034196 Opened 1 month ago Closed 1 month ago

[wpt-sync] Sync PR 59406 - Enable InitiatorUrl for ResourceTiming on dedicated and shared workers

Categories

(Core :: DOM: Performance APIs, task, P4)

task

Tracking

()

RESOLVED FIXED
152 Branch
Tracking Status
firefox152 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Guohui Deng <guohuideng@microsoft.com> wrote:

Enable InitiatorUrl for ResourceTiming on dedicated and shared workers

This CL is part of implementation of "initiator for resource timing"
feature. Explainer:
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ResourceTimingInitiatorInfo/explainer.md
Chromestatus: https://chromestatus.com/feature/4876586949804032

TaskAttribution is enabled on dedicated and shared workers to facilitate
accurate initiator tracking for resources. This allows the different
initiator URLs to be propagated across async tasks (e.g. setTimeout())
coming from different scripts(e.g. importScripts()). So, we can report
initiator with better granularity than simply reporting worker script
for all the resources and still be able to track back to the caller when
an async task fetches a resource.

There are still limitations on worker thread.

What are supported:

  1. Resources dynamically fetched by worker script, either
    directly or via a number of common async function calls
    covered by WPT tests that are added in this CL.
  2. JS files imported by "importScripts()"

What will be supported in future:

  1. Worker script itself;

What will be either supported or documented about if not supported:

  1. Modular files used in worker thread;
  2. Resources fetched in nested worker script;
  3. Resources fetched in files that are imported via
    "importScripts()".

Bug: 40919714
Change-Id: I07d6c744a0f568206404c78290d517865cb31d24
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7732189
Reviewed-by: Nate Chapin \<japhet@chromium.org>
Commit-Queue: Guohui Deng \<guohuideng@microsoft.com>
Reviewed-by: Scott Haseley \<shaseley@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1618936}

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

CI Results

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

Total 30 tests and 1 subtests

Status Summary

Firefox

OK : 25[GitHub] 30[Gecko-android-em-14-x86_64-debug-geckoview, Gecko-android-em-14-x86_64-lite-opt-geckoview, Gecko-android-em-14-x86_64-opt-geckoview, Gecko-linux2404-64-debug, Gecko-linux2404-64-opt, Gecko-windows11-32-25h2-debug, Gecko-windows11-32-25h2-opt, Gecko-windows11-64-25h2-debug, Gecko-windows11-64-25h2-opt]
FAIL : 28[GitHub] 52[Gecko-android-em-14-x86_64-debug-geckoview, Gecko-android-em-14-x86_64-lite-opt-geckoview, Gecko-android-em-14-x86_64-opt-geckoview, Gecko-linux2404-64-debug, Gecko-linux2404-64-opt, Gecko-windows11-32-25h2-debug, Gecko-windows11-32-25h2-opt, Gecko-windows11-64-25h2-debug, Gecko-windows11-64-25h2-opt]

Chrome

OK : 25
PASS : 12
FAIL : 16

Safari

OK : 21
FAIL : 24
ERROR: 4

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 152 Branch
You need to log in before you can comment on or make changes to this bug.