4 commits

Author	SHA1	Message	Date
Mark Holmquist	5df979bd65	Grand Unifying Documentation Patch ... Change-Id: Id0def78beb0231270557037a9c530c770b100ce2	2014-02-18 18:27:30 -08:00
Gilles Dubuc	8a8d74f01d	Avoid double requests when measuring performance of image load ... Change-Id: Ib5ec4c3e4e4a410a6ee520b11bf025d7447cb542 Mingle: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/207	2014-02-18 16:45:03 -08:00
Gergő Tisza	7afbc5ce92	Use provider XHR information in performance metrics + several fixes ... * more robust method of obtaining URL * decouple performance logging from providers (mostly) * ignore fake XHR object which jQuery returns for JSONP requests * guard for CORS requests - apparently Chrome refuses to return certain information even with an Allow-Origin: * response header. * Resource Timing is limited to 150 results, which causes fake misses in debug mode. There is an API to increase the limit but it is not implemented in Chrome. I am calling it nevertheless, maybe IE understands it (it is present in the MSDN docs at least). This seems to work for AJAX, CORS, JSONP, image AJAX; CORS requests return 0 for a lot of values, per spec a Timing-Allow-Origin: * header might help that. Change-Id: I8353858022f51a7e70774e65513d0fa2554a5064	2014-02-19 00:38:27 +00:00
Gilles Dubuc	e74fc33e89	Track detailed content loading network performance ... Leverages the W3C Navigation Timing API when available Change-Id: Ief1d327d1bd8928bf5f2bf0bd4c7141a0a608a53 Mingle: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/126	2014-02-07 19:37:22 +00:00