Closed Bug 1551469 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 16792 - worker: Add wpt for ResourceTiming on nested dedicated workers

Categories

(Core :: Performance, defect, P4)

Product:
Core
Component:
Performance
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla69
Tracking Flags:
Tracking Status
firefox69 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Kenichi Ishibashi <bashi@chromium.org> wrote:

worker: Add wpt for ResourceTiming on nested dedicated workers

If a worker creates a nested worker, there should be a performance
entry on the parent worker because:

  • The spec specifies that the client of "run a worker"[1] comes
    from outside settings object.
  • [2] says that a performance entry should be included in the
    performance timeline of the client's global context.

[1] https://html.spec.whatwg.org/multipage/workers.html#run-a-worker
[2] https://w3c.github.io/resource-timing/#resources-included-in-the-performanceresourcetiming-interface

Bug: 961552
Change-Id: I979f3f2e89a93545746ddd2124c931f4aa334bbc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1607714
Reviewed-by: Hiroki Nakagawa \<nhiroki@chromium.org>
Commit-Queue: Kenichi Ishibashi \<bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#658961}

Component: web-platform-tests → Performance
Product: Testing → Core
Failed to get results from try push
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/e599ff5f6d6d
[wpt PR 16792] - worker: Add wpt for ResourceTiming on nested dedicated workers, a=testonly

https://hg.mozilla.org/mozilla-central/rev/e599ff5f6d6d

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