Usage statistics to remove menu items

Yuri Khan yuri.v.khan at gmail.com
Tue Dec 26 09:43:33 UTC 2017


On Sat, Dec 23, 2017 at 9:06 PM, anatoly techtonik <techtonik at gmail.com> wrote:

> 10 years ago I filled this bug about cluttered context menu for tabs
> https://bugzilla.mozilla.org/show_bug.cgi?id=433834

> Now looking at new Firefox release this issue still appears valid to
> me. I doubt that anybody uses "Reload This Tab" and "Reload All Tabs"
> menu, and I'd like to validate my assumption, so how can I do this?

I’ll partially invalidate it for you by presenting a counterexample: I
use “Reload All Tabs”. (Although I should probably subscribe to RSS
feeds of the sites for which I use that.)

In the bug referred above, you say

> I've never used "Reload All Tabs". No idea why I would need that if I can just close and restore Firefox.

The answer to that is that you can have multiple windows and “Reload
All Tabs” only acts on tabs in the current window.

Also, restarting Firefox might or might not reload the actual pages.
Tabs are restored as “discarded”, and when you activate them, their
content may be taken from the local cache.

Additionally, consider a user with multiple workspaces, with one or
two Firefox windows on each workspace. Restarting Firefox will bring
all windows onto the current workspace and the user will have to
rearrange them back to where they belong.

You could argue that “Reload All Tabs” could be implemented as a Web
Extension, right now, without adding any new APIs, though:

    browser.menus.create({contexts: ["tab"],
                          title: "Reload All Tabs",
                          onclick: () =>
      browser.tabs.query({currentWindow: true}).then(tabs =>
        Promise.all(tabs.map(tab => browser.tabs.reload(tab.id))));
    });

Also, if you personally never use a menu item, you could hide it by
adding a userChrome.css rule, at least for as long as userChrome.css
is operational.


More information about the firefox-dev mailing list