Closed
Bug 1432837
Opened 7 years ago
Closed 3 years ago
Collect metrics for usage of menus.refresh after showing a menu
Categories
(WebExtensions :: Frontend, enhancement, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
mozilla60
People
(Reporter: robwu, Assigned: robwu)
References
Details
This is a follow-up to https://bugzilla.mozilla.org/show_bug.cgi?id=1215376#c151 Bug 1215376 added the ability to modify a context menu after it has been shown. A menu should be updated relatively soon if an extension immediately calls browser.menus.refresh in response to browser.menus.onShown in order to minimize the impact on UX. But if extensions do things like sending a network request and then trying to show the menu, then the change may be very noticeable. The purpose of this bug is to make sure that we collect metrics to determine whether the current implementation of menus.refresh is sufficient for common use cases (and in particular not having a negative impact on UX). Depending on the outcome, the API may be limited (e.g. requiring a dummy menu element to avoid visual shifts at the top-level menu) or extended (e.g. only updating submenus instead of the whole extension menu if only a submenu changes). Note to myself: There is an sample implementation of telemetry at bug 1353171.
Updated•7 years ago
|
Priority: -- → P1
Target Milestone: --- → mozilla60
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Comment 1•6 years ago
|
||
Moving to p3 because no activity for at least 24 weeks. See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P1 → P3
Updated•3 years ago
|
See Also: → https://jira.mozilla.com/browse/WEBEXT-39
Assignee | ||
Comment 2•3 years ago
|
||
There is no interest in this any more.
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•