723123 - Telemetry for time needed to switch to a tab

Status: RESOLVED DUPLICATE of bug 753127

(Firefox :: Tabbed Browser, defect)

Description

[Marco Bonardo [:mak]]

We should measure regression/hangs on time needed to switch to another tab, tat is one of the most common operation.
The initial measurement hook point sounds easy, the tabSelect event, though the final measure point is a bit foggy, should measure up to when the tab's content is actually usable by the user.

Felipe suggested separating a measure for tab switching when certain events happen, for example when some load is happening globally.

Comment 1

[Marco Bonardo [:mak]]

Attachment: test patch

so, in the end with felipe we found that we may use mozvisibilitychange on to gather the measure. Based on the specs should be a decent point, though we are unsure how our implementation interpret the specs (mostly whether it is fired before the paint or after it).
This is just a test patch made to check which kind of values are returned, usually they are around 16ms here, though we should remember on windows the common timestamp resolution is about exactly 16ms, so we may get not that useful values. The high resolution js api timer bug is not fixed yet.

Comment 2

[Marco Bonardo [:mak]]

Attachment: test patch

oops, previous one was empty

Comment 3

[:Gavin Sharp [email: [e-mail]]]

Oops, looks like we duplicated some work here. We should incorporate any relevant parts of this patch into bug 753127 or bug 790752.