Skip to content

performance.markResourceTiming is outdated #51001

@KhafraDev

Description

@KhafraDev

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions