HAR 1.3: Extra pageTimings

[Pieter Ennes]

Hi all,

In response to Jan's call for input regarding the 1.3 spec, we
currently have some private elements in the pageTimings section, some
of which may be generic enough to include them in the public
specification.

These are:

 _onProvisional: client side UI provisioning has been made
 _onCommitted: first chunk of data was seen
 _onStartRender: browser performs initial render

corresponding mainly to WebKit's signals:

WEBKIT_LOAD_PROVISIONAL
WEBKIT_LOAD_COMMITTED
WEBKIT_LOAD_FIRST_VISUALLY_NON_EMPTY_LAYOUT

I think especially onStartRender is an interesting metric, as well as
a well-defined point in time across browsers.

Pieter Ennes
WatchMouse

[Pat Meenan]

You have my vote for the render time as well - that's something I need
as well. We should make sure we cover everything included in the W3C
Navigation timing spec as well since it's cross browser, very well
defined and everyone has already agreed on it:
http://w3c-test.org/webperf/specs/NavigationTiming/

-Pat

[Pieter Ennes]

Pat,

On Mar 25, 7:13 pm, Pat Meenan <patmee...@gmail.com> wrote:
> You have my vote for the render time as well - that's something I need
> as well.  We should make sure we cover everything included in the W3C
> Navigation timing spec as well since it's cross browser, very well
> defined and everyone has already agreed on it:http://w3c-test.org/webperf/specs/NavigationTiming/

Yes, that sounds like a better way of going forward, as it would take
away the ambiguity problem w.r.t. the first two metrics I mentioned.
Next to that I'm still in favour of having a start render time as
well...

Cheers,
- Pieter

[Guy Podjarny]

I'm for start render too, we use it in Mobitest and it's well
understood on the mobile space too.

Cheers,
Guypo