- From: Ilya Grigorik <igrigorik@google.com>
- Date: Wed, 26 Aug 2015 14:12:02 -0700
- To: Ms2ger <ms2ger@gmail.com>
- Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
- Message-ID: <CADXXVKpUF2ndjkaFmBvPY_PfHxcVfb1+xOexYuuoosdWMOhL_A@mail.gmail.com>
Discussed this on the call today, need additional feedback. Please take a look here: https://github.com/w3c/navigation-timing/issues/35 thanks! On Thu, Aug 20, 2015 at 3:17 AM, Ms2ger <ms2ger@gmail.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi all, > > For example: > > > domLoading attribute > > > > This attribute must return the time immediately before the user > > agent sets the current document readiness to "loading". > > or in the Processing Model: > > > Record the time as domLoading immediately before the user agent > > sets the current document readiness to "loading". > > The "current document readiness" of what? I'm willing to accept that a > PerformanceTiming object has an implicit reference to the Window > through the Performance object from which it was retrieved (though > that should be clarified too), but even if there is a 1-to-1 mapping > from the Window object to the Document object in general, there are > exceptions. > > This issue is present both in > <https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Over > view.html> > and <http://w3c.github.io/navigation-timing/>. > > Looking forward to a clarification > Ms2ger > -----BEGIN PGP SIGNATURE----- > > iQEcBAEBAgAGBQJV1alGAAoJEOXgvIL+s8n2PH8H/3WpciRVTzvvXYUGBM9BnQUH > 4QmD7ZzMKGQtcLUW0tkZwMVIT5OGOQZZgv+2QRrbh45BuhEnOpIzvi/AEOtyNUq0 > NsojVG2168sXgzTpOHBAXy4TmjcLxpR+AOBd+lddvPyv9QlZcwtKg/DHUcnpr3sU > lR83HoDl+HVy22o68ci3aO13y38w0u8ayJoA+rI/03oo9gCa0MF04K6u+WOlXBIn > L1BFzKtmF2hr9oGCgDe3OkejZrDad4oQNxZglpqWi49sXmi9NVxoyFAMNPIkxnxo > G1UNjiC1xOR7Rz2uPK90D/kX35LvU6Za33WMjX/aD/anaZDnNhwn6HBO+39ROX8= > =4omP > -----END PGP SIGNATURE----- > >
Received on Wednesday, 26 August 2015 21:13:09 UTC