search

w3c / navigation-timing

Navigation Timing
https://w3c.github.io/navigation-timing/
Other
116 stars 30 forks source link

Reporting timestamps rely on a global object which might not exist yet #166

Closed noamr closed 2 years ago

noamr commented 2 years ago

When reporting a timestamp from FETCH/HTML, the timestamp relies on a global object (for getting the time origin). However, at that point in time the global object is either the previous global object or not yet created as it is only created upon handling of the response.

Not sure exactly how to spec this Perhaps RT should have a way of adjusting the timeOrigin after the fact, or the new timeOrigin (which is already known) can somehow be passed to FETCH and used when retrieving current high resolution time?

See also https://github.com/w3c/hr-time/issues/131

noamr commented 2 years ago

This is not a problem as time-origin creation is done at the getter. sorry for the noise.