Currently, the init and saveSuccess events (unlike all the other events) are logged server-side. This makes comparative analysis of the editing interfaces difficult (e.g. T209995).
We should switch them to be logged client-side like with the visual editor.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | MNeisler | T209995 Investigate why init->loaded drop-off is so high in desktop wikitext metrics | |||
| Open | None | T214132 Switch the 2010 wikitext editor's EditAttemptStep logging to the client side |
I'm not sure if we can without changing the meanings of them, though. At least the timings will change, and no longer really be measuring the same thing as the VE timings for the same events. E.g. init will suddenly become the same thing as ready/loaded. There's also not a great place to do saveSuccess client-side, since it'd be on the redirect to a regular article page...
If we are to do the timing the same way VE does it, then init should fire when the edit tab is clicked, and ready/loaded should fire on the edit page after init.
The main problem here is that the events take place on two different pages in the client (read/edit), but perhaps we could persist the start time in session storage?
There's also not a great place to do saveSuccess client-side, since it'd be on the redirect to a regular article page...
There's a postEdit hook that fires in the client, albeit slightly later than the when the current server saveSuccess event fires.