Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

performance.markResourceTiming is outdated #51001

Closed
KhafraDev opened this issue Dec 1, 2023 · 0 comments · Fixed by #51589
Closed

performance.markResourceTiming is outdated #51001

KhafraDev opened this issue Dec 1, 2023 · 0 comments · Fixed by #51589

Comments

@KhafraDev
Copy link
Member

Version

n/a

Platform

n/a

Subsystem

performance

What steps will reproduce the bug?

No response

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior? Why is that the expected behavior?

No response

What do you see instead?

performance.markResourceTiming only takes 5 parameters (timingInfo, requestedUrl, initiatorType, global, and cacheMode) when the spec contains those 5 and bodyInfo, status, and deliveryType.

Additional information

No response
@KhafraDev KhafraDev added performance Issues and PRs related to the performance of Node.js. and removed performance Issues and PRs related to the performance of Node.js. labels Dec 1, 2023
@KhafraDev KhafraDev mentioned this issue Jan 29, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

perf_hooks: add deliveryType and responseStatus fields KhafraDev/node
1 participant
@KhafraDev