38
edits
Mobile/Projects/Telemetry probes for Fennec UI elements: Difference between revisions
Jump to navigation
Jump to search
Mobile/Projects/Telemetry probes for Fennec UI elements (view source)
Revision as of 23:55, 21 March 2014
, 21 March 2014→Events
Oogunsakin (talk | contribs) No edit summary |
Oogunsakin (talk | contribs) (→Events) |
||
| Line 78: | Line 78: | ||
* '''action''': name of the event. Should be brief and lowercase. If needed, you can make use of namespacing with a '-' separator. Example event names: "panel-switch", "panel-enable", "panel-disable", "panel-install". | * '''action''': name of the event. Should be brief and lowercase. If needed, you can make use of namespacing with a '-' separator. Example event names: "panel-switch", "panel-enable", "panel-disable", "panel-install". | ||
* '''method''' (Optional): used for user actions that can be performed in many ways. This field specifies the method in which the action was performed. For e.g, say we want to record an event when a user adds an item to their reading list. This action can be performed by either long-tapping the reader icon in the address bar or done from within reader mode. We would use the same event name for both | * '''method''' (Optional): used for user actions that can be performed in many ways. This field specifies the method in which the action was performed. For e.g, say we want to record an event for when a user adds an item to their reading list. This action can be performed by either long-tapping the reader icon in the address bar or done from within reader mode. We would use the same event name for both actions but specify two methods: "addressbar" and "readermode". | ||
* '''extras''' (Optional): for extra information that may be useful in understanding the event. It is important to keep this very brief. | * '''extras''' (Optional): for extra information that may be useful in understanding the event. It is important to keep this very brief. | ||