Nik,
Please find comments inline.
On Sun, Oct 10, 2010 at 11:46 AM, Nik Matsievsky <speed@webo.name> wrote:
> Zhiheng --
>
> a few questions (some parts are not clear to me enough)
>
> 1. There is info only about GET method. What about HEAD / POST / PUT ?
> Maybe we should add them to spec (among 'GET equivalents').
>
At this time HTTP GET or
equivalent<http://dev.w3.org/html5/spec/Overview.html#concept-http-equivalent-get>
is
only emphasized when defining fetchStart since GET needs to check the app
cache before fetching.
Is there other places you think we should make such differentiation?
>
> 2. Chart with overall model (as it's described in chapter 4.5) will be very
> helpful. I.e. in chapter 4.2 redirects go before fetching (I hope all events
> must be placed there in proper order).
>
Yeah, that's what we agreed on in the f2f and I will have it ready soon.
>
> 3. I also hope that loadEventStart will be fired when all rendering
> activity is finished (not as now when WebKit-based browsers fire
> window.onload but some of document parts may not be rendered). Can we add
> more clarification to spec?
>
It's actually only referring to the window.onload right now. There were
discussions about adding paint-related timing but it doesn't seem to be
a reliable enough user experience benchmark in many apps.
cheers,
Zhiheng
>
>
> Hi, Folks,
>
> The NavigationTiming working draft has been updated per our f2f
> meeting on Oct. 5th.
> There are a couple unresolved issues marked as TODOs in the draft and I
> will keep this group
> post. (Philippe is probably right about working in the day off after all.
> :-)
>
> cheers,
> Zhiheng
>
>
>
> --
> Thank you,
> Nik Matsievsky, WEBO Software, www.webogroup.com
> +7 926 7281964 / skype:nikolay.matsievsky
>
>