Re: [User Timing] Spec updates

  It looks great! Two minor comments:

 - What should getMarks() and getMeasures() return if the specified key is
not available? undefined value or {}? I think it is {} but we probably want
to be more specific.
 - Shall we point the default starting point of measure() to navigationStart
give that we have it always available now?

thanks,
Zhiheng


On Mon, Apr 25, 2011 at 2:45 PM, Jatinder Mann <jmann@microsoft.com> wrote:

>  The following updates were made to the User Timing spec,
> http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/UserTiming/Overview.html:
>
>
>
> -          Fixed typos, grammatical issues and links.
>
> -          Added references to DOM Level 3 Core and ECMA-262 specs
>
> -          mark() throws a NOT_SUPPORTED_ERR exception if the name of the
> mark is the same as an attribute in the PerformanceTiming interface.
>
> -          measure() throws a NOT_FOUND_ERR exception if the name of a
> mark doesn’t exist.
>
>
>
> Please review the changes.
>
>
>
> Thank you,
>
> Jatinder Mann
>
>
>