48923 2010-11-03 09:56:09 -0700 [Web Timing] Enable by default 2017-02-10 12:25:07 -0800 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) All All RESOLVED CONFIGURATION CHANGED P2 Normal --- 42434 48922 30685 1 tonyg webkit-unassigned andyhume ddkilzer joepeck sam simon.fraser simonjam oldest_to_newest 304072 0 tonyg 2010-11-03 09:56:09 -0700 After the vendor prefix is removed, we should enable the interface by default. Assuming that the detailed timings are not passed up by the network stack for each port (bug 42432, bug 42433, bug 42434, bug 42435), we should repurpose the --enable-web-timing flag to guard just the network stack related timings (domainLookupStart, domainLookupEnd, connectStart, connectEnd, requestStart, responseStart, responseEnd) instead of the whole interface. 332761 1 tonyg 2011-01-11 16:03:51 -0800 Sam, Simon, the http://test.w3.org/webperf/specs/NavigationTiming/ has reached the last call phase and the webkit implementation is in complete compliance (as far as we are best aware). It has also been enabled for the chromium port since the Chrome 6 stable release and the Qt port for a shorter time. Do you think enabling by default in WebKit (with network stack times guarded) is the way to go or are there reasons to hold off? 1275483 2 joepeck 2017-02-10 12:25:07 -0800 It looks like all ports enable WEB_TIMING by default right now. Lets close this out.