Closed
Bug 296786
Opened 20 years ago
Closed 17 years ago
Sites are able to prevent the context menu from appearing (right-clicking doesn't work at msn.com)
Categories
(Core :: Widget: Win32, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: fehe, Unassigned)
References
()
Details
(Keywords: helpwanted, platform-parity, Whiteboard: See comment 13, comment 15)
Attachments
(2 files)
136 bytes,
text/html
|
Details | |
1.53 KB,
patch
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050604 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050604 Firefox/1.0+
I was trying to block images on www.msn.com, but they have changed their web
page code and it is instead hijacking the right-click and treating it as an left
(or "action") click.
Reproducible: Always
Steps to Reproduce:
1. Visit www.msn.com
2. Right-click an image
3. Nuff said
Actual Results:
Taken to a web page I had no intention of visiting
Expected Results:
I would prefer an override so that "normal" behavior is possible and a context
menu appears.
Comment 1•20 years ago
|
||
Firefox does have this ablity, dom.event.contextmenu.enabled is the pref and can
be enabled by tools -> options -> content -> "but disable common annoyances".
However msn seems to be getting around this pref.
> However msn seems to be getting around this pref.
Exactly. And unfortunately. :-(
Reproducible with Mozilla 1.8b1, right clicking works again if I remove:
if(tw){event.returnValue=false;i.onload=iOL;i.onerror=iOE;tid=w.setTimeout(iTO,dl);
from http://hp.msn.com/scr/home/OOB1027.js .
Interesting. It seems Microsoft may be intentionally targetting mozilla
browsers. If you use AdBlock to filter out the following javascript,
right-clicking works:
http://hp.msn.com/scr/home/msnmoz1021.js
Notice how the javascript file is called "msnmoz1021.js" (e.g. mozilla)? If you
download and take a look at that javascript, you'll notice that it is mostly
coded to control the mouse actions. Mighty nasty of them.
Is there a way of adding an option that will help a user prevent websites from
getting away with stunts like this?
Updated•20 years ago
|
Severity: enhancement → normal
Summary: Please add the abillity to filter javascripts that hijack right-clicking → Sites are able to prevent the context menu from appearing (right-clicking doesn't work at msn.com)
Comment 5•20 years ago
|
||
*** Bug 298620 has been marked as a duplicate of this bug. ***
Comment 6•20 years ago
|
||
Confirming. The msnmoz1021.js file is not the culprit, that's just a
compatibility shim. Something changed in the way we fire click events between
1.0.3 and 1.0.4 -- in 1.0.4 the site's onclick handler gets right-clicks and
unintentionally prevents the context menu, in 1.0.3 and earlier it does not.
Assignee: nobody → events
Status: UNCONFIRMED → NEW
Component: Preferences → DOM: Events
Ever confirmed: true
Product: Firefox → Core
QA Contact: preferences → ian
Comment 7•20 years ago
|
||
From my MSN contact:
Below is a very simple repro of the issue:
<script>
function doThis(ev)
{
ev.preventDefault();
}
document.addEventListener("click",doThis,false)
</script>
This incorrectly disables right click. We will be working around the issue
globally as follows:
function ValidateButton(ev)
{
if (ev.button==2) // Right mouse button - stop this event
ev.stopPropagation();
}
document.addEventListener("click",ValidateButton,true);
/be
Comment 8•20 years ago
|
||
Here is another page which prevents the context menu from working, with or
without dom.event.contextmenu.enabled set or "Disable Common Annoyances" enabled:
http://mp3-postcards.com/listen/?888
I'm using mozilla Deer Park Alpha 2 (Mozilla/5.0 (X11; U; Linux i686; en-US;
rv:1.8b3) Gecko/20050712 Firefox/1.0+)
![]() |
||
Comment 9•20 years ago
|
||
Is this still an issue? This seems to work just fine for me in a Seamonkey
trunk build on a testcase I tried and on msn.com both...
Reporter | ||
Comment 10•20 years ago
|
||
(In reply to comment #9)
> Is this still an issue? This seems to work just fine for me in a Seamonkey
> trunk build on a testcase I tried and on msn.com both...
Considering that this has not been patched, and sites like
http://demo.planzo.com and others I have not cataloged, can still get around the
Firefox "Disable or replace context menus" setting, I believe this is still an
issue.
![]() |
||
Comment 11•20 years ago
|
||
What are the steps to reproduce on that site, exactly? Hard to fix a bug if I
don't know how to trigger it...
Reporter | ||
Comment 12•20 years ago
|
||
(In reply to comment #11)
> What are the steps to reproduce on that site, exactly? Hard to fix a bug if I
> don't know how to trigger it...
Simply go to the website and right-click anywhere except on the calendar. You
should notice that the context menu does not show - unless you double right-click.
![]() |
||
Comment 13•20 years ago
|
||
Oh, I see the problem. You're on windows. So context menus fire on mouseup,
not mousedown like they do on the other platforms. So it looks like I won't be
able to actually reproduce this bug, so a minimal testcase would help a great
deal with being able to fix it...
Comment 14•20 years ago
|
||
This is a minimized testcase that resulted from going throught the code in
http://demo.planzo.com. They block the contextmenu with onclick and checking if
event.button is 2.
Click once, no contextmenu, double-click see menu. I guess the pref to disable
doesn't work because it check for oncontextmenu? Is this even a bug, or did I
misunderstood this?
![]() |
||
Comment 15•20 years ago
|
||
So it looks like the only code that fires NS_CONTEXTMENU events on Windows is
the widget code, and it does this in response to the WM_CONTEXTMENU message. I
have no idea what Windows widgetry does when processing the WM_RBUTTONUP to
prevent the WM_CONTEXTMENU from coming in in this case.... maybe it shouldn't be
returning true from ProcessMessage for right-button mouseup or something?
Comment 16•20 years ago
|
||
I see this with f1.com. Firefox 1.0.7 on Ubuntu. IMHO, site should be prevented
from doing this by default.
Comment 17•20 years ago
|
||
(In reply to comment #16)
This bug has nothing to do with f1.com, you can reenable the context menu by
edit -> preferences -> webfeatures -> advanced buton for javascript -> uncheck
allow sites to modify or replace the context menu. You still get the alert but
the context menu appears.
![]() |
||
Updated•20 years ago
|
Keywords: helpwanted
Whiteboard: See comment 13, comment 15
Comment 18•20 years ago
|
||
Yes, I realize that. I want that setting to be the default.
Comment 19•20 years ago
|
||
This is not the bug to decide if that setting should be changed. I did a quick
search in bugzilla and did not see a but filed requesting that setting to be
changed for Firefox.
Comment 20•19 years ago
|
||
I see it on http://www.snooker.pl/ - with "allow sites to modify or replace the context menu" unchecked context menu doesn't appear after alert.
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9a1) Gecko/20060121 Firefox/1.6a1 ID:2006012105
Comment 21•19 years ago
|
||
This seems to work for the event.preventDefault case, which is what the testcase attached to this bug uses.
But it doesn't work for http://www.snooker.pl/ or bug 323047.
And now that I think about it, there are probably some more methods to disallow a user to get the right-click context menu.
Reporter | ||
Comment 22•17 years ago
|
||
I have not seen this issue for a long time. Reopen if it's still a problem.
Thanks
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•