Skip to content

Unclear interactions between Resource Timing and preloads #12047

@jdm

Description

@jdm

What is the issue with the HTML Standard?

Step 4.2.8 of https://fetch.spec.whatwg.org/#fetch-finale says:

If fetchParams’s request’s initiator type is non-null, then mark resource timing

Preloads (both Link headers and link elements) do not set an initiator type (with one exception for early hints). My reading of the spec is that this means we shouldn't expect a resource timing entry for a preload request; instead there would be one generated for the consumption of the preload from a later fetch that matches it.

This contradicts the expectations of WPT tests like link-header-preload.html, which expects that the preload requests generate resource timing entries and the subsequent consumption of the preload does not. Additionally, all browsers pass these tests, which makes me very suspicious of the current specification text.

I've seen w3c/resource-timing#303, but raising this issue for this specification seemed appropriate because the actual text that needs modification is in the HTML spec.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions