You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The structure of the ResourceTiming API does not include details about the discovery time of a specific resource.
One potential use case for this new attribute is to analyze whether the Largest Contentful Paint element is discovered late during the rendering process.
The text was updated successfully, but these errors were encountered:
We talked about this in the last WG meeting, and it seems there would be some work involved in specifying exactly when "discovery" occurs (especially in the preload scanner, as that's likely not well-defined anywhere). I think that we'd also like to know what kind of support this has; whether there are enough real world use cases.
The structure of the ResourceTiming API does not include details about the discovery time of a specific resource.
One potential use case for this new attribute is to analyze whether the Largest Contentful Paint element is discovered late during the rendering process.
The text was updated successfully, but these errors were encountered: