Allow JS advanced settings to be associated with whitelists/blacklists




7 years ago
5 years ago


(Reporter: Daniel Jensen, Unassigned)


Firefox Tracking Flags

(Not tracked)




7 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20110319 Firefox/3.6.16 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20110319 Firefox/3.6.16 (.NET CLR 3.5.30729)

It'd be helpful if the capabilities set in the JS "Advanced..." option panel could be done per-site. Most of the time these capabilities are just abused, but occasionally sites will do something useful with them. Note that such functionality is outside the scope of bug 320522 / NoScript, and I'd imagine that this would be relatively hard to do with an addon (since instead of just deciding whether to load scripts this would have to change JS engine behavior per-site).

Reproducible: Always

Steps to Reproduce:
1. Go to some site where context menu replacement is abused (for instance, a site where if you right-click you get a pop-up saying "HOW DARE YOU TRY TO STEAL MY CONTENT, YOU LITTLE FIEND!!!!"). Decide you'd better disable sites' ability to mess with the context menu, and reload the page.
2. Go to a site like Google Maps where you miss out on functionality if you don't allow JS to replace the context menu. Decide you'd better enable this, and reload the page.
3. Rinse. Repeat.

Comment 1

5 years ago
I think that this should be implemented in NoScript, because it already has a good UI for per-site configuration.  If NoScript needs support in Firefox itself to do it, then it would be great if the necessary functionality were added to Firefox.  But I sure wouldn't want to have to go into the Preferences dialog to change this for every problematic site.

It is definitely an issue, though.  e.g. on Grooveshark, if I right-click, I get both the browser's and the site's context menus.  Then I have to click on the page somewhere to hide the browser's menu, and then I can use the Grooveshark one.
You need to log in before you can comment on or make changes to this bug.