958519 - [meta] Add UI Telemetry for determining menu action usage

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: General, defect)

Description

[Mark Finkle (:mfinkle) (use needinfo?)]

We need to learn more about which menu actions are used. This will help us determine what features are used and which are not. We might also be able to learn which actions are not discoverable.

We should instrument the following menus:
* Main menu
* URLBar context menu
* Home page context menu
* Content context menu

If the patches are simple enough, add them here. If not, turn this into a meta bug.

Comment 1

[Chenxia Liu [:liuche]]

Assigning this to Sola, because he'll be working on first run stuff and adding telemetry, so this is a good place to start. Take a look at bug 942279 for how to add telemetry probes.

Bug 932092 has the context for what sorts of telemetry measurements we can actually collect. Think about sessions and events, and consider what is useful.

Comment 2

[Richard Newman [:rnewman]]

Let's track use of the charset menu, mm?

Comment 3

[Mark Finkle (:mfinkle) (use needinfo?)]

My plan is to use:
Telemetry.sendUIEvent("action", "menu", getResources().getResourceEntryName(id));
or 
Telemetry.sendUIEvent("action", "contextmenu", getResources().getResourceEntryName(id));

To capture all actions. This is not a substitute for drilling into a particular feature, like tracking bookmarking or savetopdf as part of a save-for-later theme.

Comment 4

[Mark Finkle (:mfinkle) (use needinfo?)]

Main menu and Home page contextmenu are easy.

URLBar contextmenu is tied to the Main menu and we'll double count some actions if we use the easy way. Web content contextmenu is spread across the Prompt system and might not fit into the easy model either.

Therefore, I am breaking this bug up into smaller, more easily landable, bugs.

Comment 5

[Aaron Train [:aaronmt]]

Assignee reset?

Comment 6

[Richard Newman [:rnewman]]

Meta bug outlived its usefulness, I think.