W3C

- DRAFT -

Web Performance Working Group Teleconference

13 Oct 2010

See also: IRC log

Attendees

Present
AndersonQuach, NicJansma, TonyG, Zhiheng, ArvindJain
Regrets
JasonWeber
Chair
ArvindJain
Scribe
AndersonQuach

Contents


clear the agenda

list the agenda

scribe+ AndersonQuach

NicJansma: navigationStart, what about navigations without unloads?

Zhiheng: this should line up with the HTML5 spec
... Any concern with the definition fetch start?

AndersonQuach: Looks good, as long as we do not enforce undefined phases.

TonyG: Sounds good.

NicJansma: domContentLoaded split to domContentLoadedEventStart, domContentLoadEventEnd?

TonyG: Jonas brought that up, to be consistent with events.

AndersonQuach: should we added it?

TonyG: Works for me.

Zhiheng: yep.

NicJansma: navigationStart is stated after the redirect phase, should it start before redirect phase to be closer to user committing the navigation?

TonyG: the navigationStart moves is implemented in WebKit as in front of the redirect phase.

NicJansma: IE as well.
... navigationStart moved in front of redirectStart can expose the redirect phase.

TonyG: All of the folks presented on the onsite respect privacy concerns, and review with browser security team and summarize the issue on an email thread.

NicJansma: navigationStart and prompt for unload should happen prior to redirect.

Zhiheng: it is possible to have unload phase in the HTML5 spec?

TonyG: Can you share that reference?

<Zhiheng> http://dev.w3.org/html5/spec/history.html#navigating-across-documents

Zhiheng: Note in the beginning of 4.5 stating the lifetime.

NicJansma: Add one more sentence in step 1, they miss that.

Zhiheng: Good idea.

NicJansma: Step 3 in the processing model, there may be a typo. -- 3. If the current document and the previous document are not from the same origin set both unloadEventStart and unloadEventEnd to 0 then go to step 5. Otherwise record unloadEventStart as the time immediately before the unload event fires.
... What are the differences between step 5 and 6.

Zhiheng: if http
... before app cache lookup, and step 6 is not an http get.
... should these be merged?

NicJansma: Yes, it would help.
... Step 15, sub-bullet 4.. add redirectStart and redirectEnd in the exclusion list.

Zhiheng: navigationStart should point to the start of the redirect, not consistent with the diagram.

NicJansma: this section will be dependent on our joint security review.

AndersonQuach: it is our understanding that no new window object is created during a redirect. Tony is that similar to WebKit.

TonyG: Yes, no new window object is created for 300s with a subsequent 200.

Zhiheng: Graph is non-normative, itself does not have to be conformance benchmark.
... you're correct we do not have to enforce the gaps/ undefined phases.

NicJansma: Are there any other business with Navigation Timing Spec

<scribe> chair: JasonWeber

<scribe> chair: ArvindJain

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/10/13 17:16:25 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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: AndersonQuach
Inferring Scribes: AndersonQuach

WARNING: No "Topic:" lines found.

Present: AndersonQuach NicJansma TonyG Zhiheng ArvindJain
Regrets: JasonWeber
Got date from IRC log name: 13 Oct 2010
Guessing minutes URL: http://www.w3.org/2010/10/13-webperf-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]