Making Firefox's right-click not suck with about:config

Overall reaction to Firefox’s context menu

• Many find the menu long but powerful; others see it as a “junk drawer” for every feature, especially in contrived cases (e.g., right-clicking a linked image while text is selected).
• Some say Firefox’s context menu is better than macOS or Windows 11 equivalents, which are seen as slower or more cluttered.
• Several commenters note they actively use many of the criticized items (screenshots, link actions, accessibility tools, Services, etc.), while others say they’ve never used items like “Set Image as Desktop Background” or “Email Image”.

UI conventions & discoverability

• Multiple comments explain the longstanding convention that menu items with “…” open a dialog or provide an opportunity to cancel, not an immediate action.
• Strong defense of greyed-out entries: they signal that a feature exists but is currently inapplicable, preserving spatial memory and aiding troubleshooting; hiding options entirely is seen as “gaslighting” users.
• Disagreement over whether users can realistically learn such conventions and whether they remain appropriate in modern UIs.

Customization mechanisms & their limits

• Many appreciate Firefox’s flexibility: about:config flags, user.js, userChrome.css, and extensions can strip or rearrange menu entries.
• Some prefer disabling features via about:config; others argue for keeping features enabled and only hiding specific menu items via CSS or tools like SimpleMenuWizard.
• Several call for a first-class GUI editor (“Customize context menu”), similar to Firefox’s toolbar customization or other browsers’ menu editors, rather than relying on cryptic prefs.
• Complaints that about:config is poorly documented, hard to search, and more opaque after recent changes; calls for integrated documentation, tooltips, or a wiki-like system.

AI, bloat, and privacy concerns

• Strong pushback against AI/chatbot and visual search options appearing by default in the menu; seen as bandwagon “bloat” and contrary to Firefox’s privacy image.
• Others counter that these features are opt-in at the moment of use and don’t send data until explicitly invoked.
• Some see the prominent “Remove AI chatbot” entry as both an admission of controversy and the right way to handle polarizing features.

Broader UX and cultural points

• Debate over dense “professional” interfaces vs minimal “casual” ones, and how to serve power users without overwhelming others.
• References to menu bars, Fitts’s law, context menus, and keyboard shortcuts as overlapping mechanisms for discoverability and speed.
• A few note the increasingly angry tone of such critiques, tying it to broader frustration with modern, perceived-as-hostile software design.