Histograms to track shortcut behavior |
|||||
Issue descriptionWe currently do not track usage of keyboard shortcuts in Chrome. We have some access to this information (for ex. control-T we can somewhat figure out by subtracting wrench menu new tabs from overall new tabs. However this is awkward and this is likely not available for all shortcuts. It would be best is the UX was instrumented as a histogram (1 enum per shortcut) so we could easily do UX analysis. (not sure if right component)
,
Apr 14 2017
,
Apr 16 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 16 2018
cc'ing Mark as new desktop UI PM, since this feels desktop UI-y and I'm sure he's thinking about metrics for other tab related things
,
Jun 8 2018
I'm not sure what decisions we would make with this data. Closing for age, but reopen if there are insights that we need from data we don't have.
,
Jun 8 2018
I remember there were explorations we were doing about the different access points for opening new tabs (keyboard shortcut, button in the tab strip, right click context menu on a tab, etc.) But I don't remember exactly what those were. Maybe Alex or Rob remember? :)
,
Jun 8 2018
Cool. The tab opening metric was pretty easy to understand in the data since it so overwhelmingly NOT keyboard shortcut. :)
,
Jun 13 2018
Honestly I don't really remember why I filed it. My guess was maybe Alex had thought it would be useful? If current team isn't interested than we can just mark obsolete
,
Jun 13 2018
At some point I think we were trying to figure out if power / heavy user population predominantly use shortcuts over the corresponding context / app menu item. It might have been related to the organisation of menus. If usage is mainly through shortcuts then maybe they don't need to be at the top level. Some of our editing context menus in particular are very tall. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ainslie@chromium.org
, Sep 15 2016