Top
Best
New

Posted by mmsc 4 hours ago

Making Firefox's right-click not suck with about:config(joshua.hu)
196 points | 135 commentspage 2
aftbit 4 hours ago|
Odd complaint but interesting list of about:config options! I must be in the tiny minority that has actually _used_ all of these right-click menu items at one time or another.
yreg 4 hours ago|
I mean "Set as Desktop background" seems to definitely be an overkill to have on a speed dial.

Unfortunately that one is not removable through about:config.

debugnik 4 hours ago|||
That one gets used a lot when someone leaves their laptop unlocked at college.
plorkyeran 2 hours ago|||
That one's been there since the very early days of Netscape Navigator. It's been a few decades since I last clicked on it, but that's mostly because I haven't set my desktop wallpaper in a few decades and I suspect using that isn't too rare for the people who do set wallpaper?
bigthymer 4 hours ago||
Personally, I think the Firefox browser right-click options are one of the more useful right-click menus. The one on the Apple OS is a better example of excessive and worthless.
peterspath 4 hours ago|
I really miss the look up, translate, and search with... options in Firefox I have anywhere else when I right click on a selected word.
tcfhgj 4 hours ago||
interestingly, I have these options in Firefox
OkayPhysicist 3 hours ago||
I think the above comment meant that he misses those Firefox options when he uses other applications.
oniony 1 hour ago||
There are actually eight dividers.
lifis 1 hour ago||
The improvement that could be made is to reorganize the menu so that entries are grouped in "Image", "Link", "Text", "Page" and "Development" sections, which could either be submenus or titled sections depending on screen size and user preferences
mantra2 4 hours ago||
I wish they had an always up to date guide on what each about:config option does.
alpaca128 4 hours ago|
Or make them more discoverable. I spent so much time looking for a UI scaling setting, and in the end it turned out its name does not contain any obvious word like scale or size, instead it is called devPixelsPerPx. It isn't even consistent about Pixels vs Px.
1718627440 1 hour ago||
> It isn't even consistent about Pixels vs Px.

px is the CSS unit, device pixels aren't.

alpaca128 1 hour ago||
Good to know it has some logic to it, thanks for the clarification
SllX 3 hours ago||
All those items in the context menu are one of the reasons that context menus are so good. Ideally you never need to go to the menu bar for much of anything because the right menu item is right there in the context menu where your cursor is already aiming.
LikeBeans 2 hours ago||
A while back I wanted more menu options with Firefox so I made an extension [1]. Basically when you highlight a word or a sentence on a page a menu popups up with some options like to copy, search, or lookup on Google maps. Or whatever option you want. I use it often and find it useful.

[1] https://addons.mozilla.org/en-US/firefox/addon/popup-tooltip...

1718627440 1 hour ago|
> Basically when you highlight a word or a sentence on a page a menu popups up with some options like to copy, search

Huh, beside Google Maps, that's what the default context menu does in Firefox?

LikeBeans 1 hour ago||
Yeah the Google Maps was my primary goal. But I was also thinking a person can add other options. For example different search engines. Or maybe your favorite AI agent search.
adamtaylor_13 1 hour ago||
Does uBlock Origin do something like this by default? I noticed that my right-click menu looks completely sane; almost identical to the end, clean result. But I've never done this particular config cleanup before.
g947o 3 hours ago||
I wonder when was the last time any user used the "Email image" feature.
qbrass 1 hour ago|
Intentionally? I've only ever "used" it when trying to copy a link to an image.
chrismorgan 4 hours ago|
Long ago, I culled some items from the context menu via userChrome.css.

1. In about:config, turn pref toolkit.legacyUserProfileCustomizations.stylesheets on.

2. Create chrome/userChrome.css in your profile directory (which you can find from about:support).

3. Open the Browser Toolbox with Ctrl+Alt+Shift+I or ≡ → More tools → Browser Toolbox or Tools → Browser Tools → Browser Toolbox or some such thing. This is dev tools for the browser.

4. In the Inspector tab, search #contentAreaContextMenu to navigate to the <menupopup id="contentAreaContextMenu" …> element.

5. Look through its children. Decide which ones you don’t want, then kill them in CSS.

From my userChrome.css (I think this must be something like a decade old because I started typing curly quotes somewhere around then):

  /* I don't want *two* items for Inspect, just the one main one please. */
  #context-inspect-a11y,
  /* I'm happy to use Ctrl+Shift+S; I don't need a context menu item for it. */
  #context-take-screenshot,
  #context-sep-screenshots,
  /* I don't use Firefox's password manager. */
  #fill-login,
  #fill-login-generated-password,
  #manage-saved-logins,
  #passwordmgr-items-separator {
      display: none;
  }
The article takes the approach of disabling features (e.g. devtools.accessibility.enabled). I take the approach of leaving the features enabled (I want the accessibility stuff!) and just removing the specific context menu item that I found annoying.

(… and I see at the end of the article that this approach is what the next post is to be about. Heh. Posted before reading to the end. Probably would still have posted roughly the same thing.)

sunaookami 36 minutes ago||
Important for macOS: You must set "widget.macos.native-context-menus" to "false" or else you can't inspect/modify the context menu through userChrome.css.
OkayPhysicist 3 hours ago||
The other great use for userChrome is reclaiming the space at the top of the browser if you use tree-style tabs. With just the url bar, the window is close enough to full-screen when I close the tab tree that I rarely feel the need to use F11.
More comments...