-
-
Notifications
You must be signed in to change notification settings - Fork 37.1k
performance.getEntriesByName ignores optional type argument #54766
Copy link
Copy link
Closed
Labels
perf_hooksIssues and PRs related to the perf_hooks module and performance measurement APIs.Issues and PRs related to the perf_hooks module and performance measurement APIs.web-standardsIssues and PRs related to web-platform APIs and standards compliance.Issues and PRs related to web-platform APIs and standards compliance.
Description
Activity
Metadata
Metadata
Assignees
Labels
perf_hooksIssues and PRs related to the perf_hooks module and performance measurement APIs.Issues and PRs related to the perf_hooks module and performance measurement APIs.web-standardsIssues and PRs related to web-platform APIs and standards compliance.Issues and PRs related to web-platform APIs and standards compliance.
Version
v16.7.0 - v22.7.0
Platform
Subsystem
perf_hooks
What steps will reproduce the bug?
Executing this script:
How often does it reproduce? Is there a required condition?
100% of the time
What is the expected behavior? Why is that the expected behavior?
As per:
The expected behaviour is:
What do you see instead?
Additional information
This bug appears to have existed since
performance.getEntriesByNamewas added as part of performance timeline spec compliance in v16.7.0.#39297 introduced
performance.getEntriesByNamewithout a type argument. While thetypeargument was subsequently added to the underlyingobserve.getEntriesByNamemethod in #39532, it was never passed through byperformance.getEntriesByName.