Re: Making sense of the various web performance specifications

• From: Boris Zbarsky <bzbarsky@mit.edu>
• Date: Tue, 16 Jun 2015 12:34:59 -0400
• To: Ilya Grigorik <igrigorik@google.com>, Todd Reifsteck <toddreif@microsoft.com>
• CC: Philippe Le Hegaret <plh@w3.org>, "public-web-perf@w3.org" <public-web-perf@w3.org>
• Message-ID: <55805033.8040307@mit.edu>

On 6/16/15 11:48 AM, Ilya Grigorik wrote:
> They're tangled together. Practically speaking, you can't implement one
> without the other:
> - HR-time defines time origin and performance.now().. but that presumes
> Performance interface exists.
> - Perf Timeline, in turn, needs time origins and performance.now()

There's no particular reason things couldn't be set up like so:

HR-time: defines time origin, DOMHighResTimestamp, and a Performance 
interface with a single now() method.

Perf Timeline: depends on HR-time, defines a "partial interface 
Performance" with the bits it wants to add.

> I guess we could keep definition of DOMHighResTimestamp in HR-time (its
> use doesn't have to be limited to perf specs), but move definition of
> time origin and performance.now into Perf Timeline.

The definition of DOMHighResTimestamp is pretty much tied to the 
definition of time origin.

-Boris

Received on Tuesday, 16 June 2015 16:35:30 UTC