performance - Navigation Timing API domInteractive fired before responseEnd (dom interactive fired before response end) -
according navigation timing api documentation, dom interactive triggered when whole document parsed. responseend triggered when last byte of response received. looking @ our real world data (visitors site) saw numerous cases dom interactive events happens before response end event, in internet explorer 9+. thoughts?
actually, spec says 'this attribute must return time before user agent sets current document readiness "interactive".' can interactive before loaded. however, in data, msie sets property before others. others seem set @ or near domcontentloadedeventstart. perhaps better metric use rather dominteractive.
Comments
Post a Comment