Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Account for ServiceWorker startup time #7

Closed
igrigorik opened this issue Nov 7, 2014 · 1 comment
Closed

Account for ServiceWorker startup time #7

igrigorik opened this issue Nov 7, 2014 · 1 comment

Comments

@igrigorik
Copy link
Member

(based on discussion at TPAC..) /cc @slightlyoff

  • The request may be blocked on SW startup and NavTiming should provide visibility into this.
  • fetchStart is when we send request to worker, SW startup time should be captured before that.

How about [swStartupStart, swStartupEnd], between "Negotiate Link" and "redirect"? See processing model.


P.S. Once we agree on the language, same logic should be replicated in Resource Timing - the worker can be killed between requests; we can't rely on SW being there. Also, UT and RT will be exposed in SW (see w3c/ServiceWorker#553), so I assume we will simply report 0's for startup time when inside a SW.

@igrigorik
Copy link
Member Author

Resolved by 979980b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant