RE: Last Call for High Resolution Time Level 2

Aside from the now() method, the Performance interface also has Navigation, Resource, and User Timing methods and attributes defined on it. Currently, the expected behavior for the Timing APIs hasn't been defined in the Web Workers scope. E.g., in a shared worker what should Resource Timing return? The timing related to resources downloaded in any of the documents sharing the worker, only resources initiated in the shared worker, or none of them? While the Working Group plans on eventually defining the Timing behavior in Web Workers in the different Timing specs, by creating a separate WorkerPerformance interface we can ensure that the High Resolution Time Level 2 spec is only defining the now() method in the worker scope.


-----Original Message-----
From: [] On Behalf Of Anne van Kesteren
Sent: Wednesday, December 4, 2013 6:47 AM
Cc: public-webapps
Subject: Re: Last Call for High Resolution Time Level 2

On Tue, Dec 3, 2013 at 3:51 PM, Philippe Le Hegaret <> wrote:
> interface WorkerPerformance {
>   DOMHighResTimeStamp now();
> };

Is there any particular reason the Performance interface itself cannot be used? It seems somewhat cumbersome to have to prototype different interfaces (if you're into that kind of thing) depending on the global environment you're in.


Received on Wednesday, 4 December 2013 19:05:52 UTC