RE: Update of Navigation Timing CR draft

The constant PERF_NAVIGATION was initially added for use with the Performance Timeline model - the getEntriesByType and getEntriesByName take an entryType that describe the type of performance metric requested. Initially, entryTypes were shorts and required integer constants. We later changed most constants to strings, but it appears this one was missed.

Per ACTION-59, we are removing all string constants. As a part of that change, I have removed all constants (e.g., PERF_RESOURCE, PERF_DEVELOPER_MARK, and PERF_DEVELOPER_MEASURE). Instead, one can call getEntriesByType with a string directly. E.g., getEntriesByType("resource").

I think it's safe to say we can remove PERF_NAVIGATION from Navigation Timing. Section 4.5 The PerformanceTiming interface in the Performance Timeline spec, http://www.w3.org/TR/2011/WD-performance-timeline-20110811/, should define what the PerformanceEntry for Navigation Timing looks like.

Jatinder

-----Original Message-----
From: Philippe Le Hegaret [mailto:plh@w3.org] 
Sent: Wednesday, January 11, 2012 11:55 AM
To: Zhiheng Wang
Cc: public-web-perf
Subject: Re: Update of Navigation Timing CR draft

Zhiheng,

what is PERF_NAVIGATION in Navigation Timing? It has been introduced since June last year and its meaning is not defined in the spec. Are we using it somewhere?

Philippe

[1]
http://www.w3c-test.org/webperf/specs/NavigationTiming/#sec-window.performance-attribute

Received on Wednesday, 11 January 2012 21:38:47 UTC