Closed Bug 566286 Opened 14 years ago Closed 13 years ago

context menu disabled even though dom.event.contextmenu.enabled=false and JavaScript is off

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: franz.gans, Unassigned)

References

(
URL
)

Details

(Whiteboard: [CLOSEME 2011-1-30]) 

User-Agent:       
Build Identifier: FF 3.5.9

With initially active JavaScript it is impossible to activate the context menu which usually appears when you right-click on an image.

Reproducible: Always

Steps to Reproduce:
1. With active JavaScript and dom.event.contextmenu.enabled=false open the URL
   http://picturesque.phanfare.com/4506587
2. click right on the big image in the center
3. observe a pop-up saying "This function is disabled"
4. disable JavaScript
5. click again
6. observe again.
Actual Results:  
The context menu is not accessible, the pop-up says "This function is disabled"

Expected Results:  
(a) Honour the disabled setting "Das Kontextmenu deaktivieren oder ersetzen" (dom.event.contextmenu.enabled=false) [preferred]
(b) Remove the Option "Das Kontextmenu deaktivieren oder ersetzen" (dom.event.contextmenu.enabled)
Dupe/related to bug 330756.
The site is using Yahoo User Interface Library (YUI) to disable the context menu.
YUI is a JavaScript Library. Why is code fromm a JavaScript library executed when JavaScript is turned off?
The pref does not disable JavaScript. It stops some ways to disable the context menu from working.
Kevin! There two issues:

1. Please read "Steps to Reproduce" #4: "disable JavaScript"
That means: Edit - Preferences - Content - [ ] Enable JavaScript

Questions: (a) Does that imply that JavaScript is now disabled?
           (b) If so, why is site-supplied JavaScript executed when
               a right-click is performed?

You may even skip steps 2 und 3 to see the effect.

2. The setting "dom.event.contextmenu.enabled" is user-visibly announced
as 

Edit - Preferences - Content - Advanced - [ ] Disable or replace context menus

According to my understanding of natural language this implies that ALL and not only SOME attemps to disable or replace the context menus are to be blocked.

FF breaks the promise not to let the originator of the content determine where the user is "allowed" to activate the context menu.
Another testcase:

http://developer.yahoo.com/yui/examples/menu/contextmenu_source.html

With enabled JavaScript and disabled dom.event.contextmenu.enabled 3.7a5pre displays the original context menu above the site-supplied one, which is IMHO OK. That's the behavior well knowm from say google maps.

3.6.3 also works that way.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
http://picturesque.phanfare.com/4506587

The page has changed: There is no longer a popup saying "This function is disabled".

FF 4 and 3.6.13 successfully prevent the suppression of the context menu when contextmenu.enabled=false.
You need to log in before you can comment on or make changes to this bug.