search

w3c / navigation-timing

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

Should processing model cut the steps defined by PerformanceResourceTiming? #78

Closed toddreifsteck closed 2 years ago

toddreifsteck commented 7 years ago

At TPAC 2017, we realized that the steps in Navigation Timing 2 often are copies of PerformanceResourceTiming. Can we point to Resource Timing rather than having copy/paste?

igrigorik commented 6 years ago

The challenge is that while NT does follow the same high-level logic flow, it also instruments different sub-steps with different and additional timing attributes related to lifecycle of the document, as well as how it treats redirects — e.g. NT exposes redirectCount, whereas RT does not. In short, possible, but we can't simply defer to existing RT processing algorithm as is; we'd need to do some refactoring in both specs.

yoavweiss commented 6 years ago

This doesn't seem like a blocker to shipping L2. Correct?

igrigorik commented 6 years ago

Per the text we added to our new charter...

Note: after Level 2 of Navigation Timing is ratified, future development of new Navigation Timing features will be done within Resource Timing; Navigation Timing will be merged with Resource Timing.

Updated to L3.

yoavweiss commented 2 years ago

@noamr - I suspect this is obsolete.. Can we close in your opinion?

noamr commented 2 years ago

@noamr - I suspect this is obsolete.. Can we close in your opinion?

Yes