4 commits

Author	SHA1	Message	Date
Reedy	5c3846a74b	Drop execute bit ... Change-Id: I6c9f8ea6251bf6a7ed2a5684e5eaa572530a4fb9	2014-06-30 18:34:02 +01:00
Gergő Tisza	8b984c5ed4	Minor documentation tweaks ... Change-Id: I8b513ceab06ddeb47261949061b777105cfa7b65	2014-02-21 00:45:06 +00:00
Mark Holmquist	5df979bd65	Grand Unifying Documentation Patch ... Change-Id: Id0def78beb0231270557037a9c530c770b100ce2	2014-02-18 18:27:30 -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