- From: Philippe Le Hegaret <plh@w3.org>
- Date: Thu, 06 Sep 2012 08:12:25 -0400
- To: "Reitbauer, Alois" <Alois.Reitbauer@compuware.com>
- Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
On Thu, 2012-09-06 at 07:07 +0000, Reitbauer, Alois wrote: > For me it seems to be simply wrong; at least when I read the > specification. Any chance that you'd be willing to write a test to illustrate this? Philippe > > // Alois > > > From: James Simonsen <simonjam@chromium.org> > Date: Thursday, September 6, 2012 1:26 AM > To: Alois Reitbauer <alois.reitbauer@compuware.com> > Cc: "public-web-perf@w3.org" <public-web-perf@w3.org> > Subject: Re: Understanding Navigation Timing Metrics > > > > I can only guess: maybe it's document.open? > > > James > > > On Wed, Sep 5, 2012 at 6:30 AM, Reitbauer, Alois > <Alois.Reitbauer@compuware.com> wrote: > Looking at some real world Web performance data, I found an > interesting issue. > > > According to the specification DOM Interactive is triggered > when the whole document is parsed. ResponseEnd is triggered > when the last byte of the response is received. Looking at our > real world data I saw numerous cases where the DOM Interactive > events happens before the Response End event. Any thoughts on > this? > > > // Alois > > > > > On Wed, Sep 5, 2012 at 6:30 AM, Reitbauer, Alois > <Alois.Reitbauer@compuware.com> wrote: > Looking at some real world Web performance data, I found an > interesting issue. > > > According to the specification DOM Interactive is triggered > when the whole document is parsed. ResponseEnd is triggered > when the last byte of the response is received. Looking at our > real world data I saw numerous cases where the DOM Interactive > events happens before the Response End event. Any thoughts on > this? > > > // Alois > >
Received on Thursday, 6 September 2012 12:12:36 UTC