mediawiki-extensions-Visual.../modules/ve-mw/init/targets
Roan Kattouw 86b82b537d Make activation timings sent to EventLogging not lie
The activation timing was always a bit of a lie even pre-TargetLoader,
because the timer only started when the first RL request for VE
modules had loaded. But at least the process it covered was consistent,
which is no longer true with TargetLoader. Now that we start the
request for the HTML together with the RL request, the activation
time might include some, all or none of the HTML request depending
on how fast the RL request was.

This change makes the activation timings more useful by measuring
from the moment the user clicks "edit" to the moment the editor
is done loading, which is what actually matters.

* Moved start of activation timing to VPT init
** For mobile this falls back to when mw.Target#load is called;
   we'll have to fix that in MobileFrontend later
* Moved end of activation timing out of TargetEvents#onSurfaceReady
  into individual onSurfaceReady handlers
** This is necessary because VPT's onSurfaceReady does quite a lot,
   and we want to include the time that takes in our measurements

Change-Id: Ie44f0b839b39a2b3b22dcd86e20f0d1170cb6069
2015-04-14 21:57:11 +00:00
..
ve.init.mw.MobileViewTarget.js Make activation timings sent to EventLogging not lie 2015-04-14 21:57:11 +00:00
ve.init.mw.ViewPageTarget.init.js Make activation timings sent to EventLogging not lie 2015-04-14 21:57:11 +00:00
ve.init.mw.ViewPageTarget.js Make activation timings sent to EventLogging not lie 2015-04-14 21:57:11 +00:00