Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This is something that's commonly abused, so I almost always want it to be off, except when I'm using a handful of large webapps that use the feature properly, such as Google Docs. I know there's a universal toggle for this in the Firefox preferences; but is there a way to grant this privilege only to certain domains? Something like a whitelist?

share|improve this question
I would really like to know this as well! – Cerberus Feb 15 '12 at 8:27
I have found a way, through a Greasemonkey script! See here:… – Cerberus Jul 1 '12 at 22:16

you can try no-script Addone for firefox and allow the script on the few sites you want. You also can enable each script file saparate if you want.

EDIT: If you only want to block the contextmenu itself you can follow these steps:

edit-> preferences -> content -> advanced options of JScript -> set the toggle to "disable or replace context menu"

share|improve this answer
The No-Script Addon will let you enable Javascript on a per-site or per-domain basis, and has it off by default. When you encounter a site you can enable scripting by clicking on its icon in the statusbar. It's exactly what you want. – LawrenceC Feb 15 '12 at 12:27
But Kenny, this is not site-specific. @Ultra: Noscript is site-specific, but it doesn't allow you to allow all Javascript except context-menu changes, which is what we're looking for. – Cerberus Mar 15 '12 at 11:42

i know this is an old question, but it's exactly the one i've been trying to find an answer for, and the ones here don't seem to fully satisfy the original question.

It appears to me the only way to regulate just context menu access to specific sites is using Firefox's "hidden" CAPS feature:

It can be tricky to manage the policies, and any time you want to add a new site to the list, you have to edit the user.js file & restart Firefox.

i'm not really a fan of using add-ons to manage built-in features, since i want the policies to be persistent & i see no reason to let Firefox suck even more memory for an add-on i'll rarely utilize once my settings are established.

The only question i have about doing this through CAPS is how to address the actual context menu option.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .