Closed Bug 1805531 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 37486 - Use SecurityOrigin when getting cross-frame same-origin performance entries

Categories

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

task

Tracking

()

RESOLVED FIXED
110 Branch
Tracking Status
firefox110 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Jaspreet Sandhu <jaspreetsandhu@google.com> wrote:

Use SecurityOrigin when getting cross-frame same-origin performance entries

This change adds logic to compare child-frame origins with the frame that calls the Performance Timeline methods, instead of defaulting to the top of the frame tree.

This addresses the case where a remote frame, that isn't the top-level frame, tries to get entries from a subframe that is local to the top-level frame.

Change-Id: I7f6a10f7c3438b970746078b3e97f5c05f13af6f
Reviewed-on: https://chromium-review.googlesource.com/4097824
WPT-Export-Revision: 7e6ddb32a49b7acf127e9cf2098d04f6005af09c

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

CI Results

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

Total 4 tests and 1 subtests

Status Summary

Firefox

TIMEOUT: 4
ERROR : 4

Chrome

TIMEOUT: 4
ERROR : 4

Safari

TIMEOUT: 4
ERROR : 4

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6d40bfa26b93 [wpt PR 37486] - Use SecurityOrigin when getting cross-frame same-origin performance entries, a=testonly https://hg.mozilla.org/integration/autoland/rev/8a3f72ac01c8 [wpt PR 37486] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 110 Branch
You need to log in before you can comment on or make changes to this bug.