See also: IRC log
<scribe> scribe: Jatinder Mann
move to agenda 1
agenda move to 1
move to agenda 1
- http://lists.w3.org/Archives/Public/public-web-perf/2011May/0046.html
- Zhiheng: Want to keep measures, just want it to be more coherent with mark and measures. Measures is important because it gives a standard interface.
Zhiheng: Follow up with Tony and James to see if they can propose a way to make measure and marks work better together.
Jatinder: The "type" attribute and getResourceTimingsByType method provide users with a simple way to roughly sort their resource timing data by the initiator types. As some initiators, like XHR and Script, can load additional resources, it is useful and practical for web developers to sort their resources by the type of initiator. The initiator type will not change over time. The "type" attribute doesn't suffer from the problems of the "id" attribute a
Christian: Agree.
Tony: What type in particular would you want to look at?
Jatinder: An example would be if you are pulling video and images resources from a news site, the URLs would typically look the same. Here pulling by Type is useful.
We have agreed to keep the type data in the array, but remove the getResourceTimingsByType accessor.
Jatinder: Do not want to require
Resource Timing to be explicitly enabled by web
developers.
... Our joint analysis,
http://lists.w3.org/Archives/Public/public-web-perf/2010Dec/0024.html,
had shown that the impact of keeping Resource Timing enabled is
negligible. The average number of resources per page is 42 and
the 90th percentile is 145. The benefit of having Resource
Timing enabled by default will mean that web pages using
analytics libraries will have to make no explicit change to use
Resource Timing. Otherwise, all analytic library users w
... Resource timing.
... We agree that the Resource Timing should be on by default,
however, the maximum number of resources captured by default
should be reduced from 1000 to a smaller number.
Action Jatinder to analyse data to see what the recommended buffer size should be.
<trackbot> Created ACTION-25 - Analyse data to see what the recommended buffer size should be. [on Jatinder Mann - due 2011-05-11].
move to next agenda
http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/ResourceTiming/Overview.html#processing-model
Jatinder: Let's review the Processing Model.
James: Let's remove fetchEnd or responseEnd from the timing, as they are redundant.
Jatinder: Let's be consistent with Navigation Timing and cut fetchEnd.
Tony: The processing model doesn't seem to have the cross-origin details that navigation timing has.
James: I prefer resourceStart rather than resourceFetchStart.
Jatinder: Agreed.
Chrisitian: The processing model should be clear that secureConnectionStart is optional.
move to next agenda
<jamesr> hmm
<jamesr> i think zakim thinks i am TabAtkins
<jamesr> yeah he must use the same phone
<jamesr> that'll mess him up on the next CSS call :)
http://lists.w3.org/Archives/Public/public-web-perf/2011May/0045.html
Action Jatinder to check whether to name the API window.visible, document.visible, window.pageVisible and document.pagVisible.
<trackbot> Created ACTION-26 - Check whether to name the API window.visible, document.visible, window.pageVisible and document.pagVisible. [on Jatinder Mann - due 2011-05-11].
Jatinder: Changes I made: Window
rather than Navigator implements WindowVisibility
interface.
... updated the event name to visibilitychange.I have also
specified that this event can only be registered using
addEventListener on window; this implies that this event can’t
be exposed using onvisibilitychange.
Cameron: Let's see if we can follow up and see what the value is for keeping onvisibilitychange.
Jatinder: I have generalized the
definitions of visibility from my previous very specific cases.
I have defined page visibility as the visibility state of the
Document contained by the top level browsing context.
... I have combined the two preview states to a single
PAGE_PREVIEW state. Per Alex’s initial email on page
visibility, he had shown interest in a page preview state:
http://lists.w3.org/Archives/Public/public-webapps/2011JanMar/0175.html.
JamesR: What's the value of having PAGE_OTHER?
Jatinder: Will follow up and see
if there was a historical reason for having a reserved
constant.
... I have updated the example section with more description
and an updated example. The updated example is a skeleton case
of throttling checking for email when not visible. Let me know
if you have any better examples in mind.
move to next agenda
Jatinder: I understand that a browser may not be able to guarantee that a callback will occur. We should attempt to specify match the number of callbacks with the refresh rate of the display.
JamesR: Will update the spec to cover the callback rate.
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: JatinderMann Found Scribe: Jatinder Mann Default Present: [Microsoft], +1.650.253.aaaa, +1.650.691.aabb, +44.207.184.aacc, +1.650.214.aadd, heycam, jamesr Present: [Microsoft] +1.650.253.aaaa +1.650.691.aabb +44.207.184.aacc +1.650.214.aadd heycam jamesr Jatinder Mann Zhiheng Arvind TonyG JamesS Christian Agenda: http://lists.w3.org/Archives/Public/public-web-perf/2011May/0047.html WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 04 May 2011 Guessing minutes URL: http://www.w3.org/2011/05/04-webperf-minutes.html People with action items:[End of scribe.perl diagnostic output]