- From: Anderson Quach <aquach@microsoft.com>
- Date: Thu, 9 Dec 2010 23:07:19 +0000
- To: "public-web-perf@w3.org" <public-web-perf@w3.org>
- CC: Simon Pieters <simonp@opera.com>, Bryan McQuade <bmcquade@google.com>, Zhiheng Wang <zhihengw@google.com>, Jonas Sicking <jonas@sicking.cc>
- Message-ID: <1E1FF4102DEA7A40AF9CC342044ECE5D2E30CD98@TK5EX14MBXW603.wingroup.windeploy.ntde>
Hi Folks, In the meeting on 12/1/2010 [minutes<http://www.w3.org/2010/12/01-webperf-minutes.html>], as a working group we decided to go with window.performance as the official namespace for the Web Performance Working Group. We reviewed the risks of this name and its alignment to the working group's charter. The decision was based on a number of different factors: i. The namespace performance is much more suitable given the direction we want to take with this working group in terms of helping site operators and site developers access and understand their performance in user agents. Particularly as we move forward with adding functionality to this interface. The alternate names we considered were pagePerformance and webPerformance. ii. The risks as outlined in Zhiheng's response and in our previous study on high traffic sites were found to be low for the name "performance". iii. When analyzing the occurrences of pagePerformance, the analysis came back inconclusive, no concrete instances of "var pagePerformance" or "var webPerformance" were found. Best Regards, Anderson Quach IE Program Manager From: public-web-perf-request@w3.org [mailto:public-web-perf-request@w3.org] On Behalf Of Zhiheng Wang Sent: Tuesday, November 23, 2010 2:50 PM To: Jonas Sicking Cc: Simon Pieters; Bryan McQuade; public-web-perf@w3.org Subject: Re: [NavigationTiming] Move window.performance to navigator.performance So "pagePerformance" sounds good to everyone? Nic and Anderson found that 0.00993% of high traffic websites has performance object in their scripts. It might not cover all the cases, but I sort of subscribe to the idea that these developers should know about this draft, especially if they care about "performance". };-> That said, using a rarer name helps. cheers, Zhiheng On Tue, Nov 23, 2010 at 12:05 PM, Jonas Sicking <jonas@sicking.cc<mailto:jonas@sicking.cc>> wrote: On Tue, Nov 23, 2010 at 11:58 AM, Simon Pieters <simonp@opera.com<mailto:simonp@opera.com>> wrote: > On Tue, 23 Nov 2010 19:34:54 +0100, Bryan McQuade <bmcquade@google.com<mailto:bmcquade@google.com>> > wrote: > >> Agree that the property name performance is likely to collide with >> existing >> scripts. Maybe we need to choose a different less common name? > > That works for me. Any suggestions? "pagePerformance" doesn't come up much > in google code search. Sold! / Jonas
Received on Thursday, 9 December 2010 23:08:44 UTC