-
Notifications
You must be signed in to change notification settings - Fork 30
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
Clarify ServiceWorker time origin #1
Comments
Current spec:
Feedback from Kinuko Yasuda and Jake Archibald:
https://w3c.github.io/hr-time/#sec-examples seems to imply that current difference in definitions is born out of convenience: "A developer may wish to construct a timeline of their entire application, including workers. With a dedicated worker, this is easy. All DOMHighResTimeStamps recorded in the worker use the same time origin as the document." Perhaps we can/should simplify the time origin to be consistent between Dedicated and Shared Workers? |
(as discussed at TPAC...)
@slightlyoff I believe current language should be sufficient for ServiceWorker, correct?
That said, I think we may need to refine
workerStart
:Since there is no "current document" (there can be multiple) for ServiceWorker, above doesn't really work. Perhaps add a clause for "if there is no current document, or there are multiple, then report time from worker start"?
The text was updated successfully, but these errors were encountered: