Open Bug 278618 Opened 20 years ago Updated 2 years ago

"alert()" should be skipped when circumventing context menu disabling

Categories

(Core :: DOM: Core & HTML, defect, P5)

x86
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: palaste, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913

Some web pages use cute Javascript tricks to prevent the user from accessing the
context menu, apparently thinking all the world's MSIE. This is frequently done
by setting the "on right click" action to a Javascript alert() call. Now
Mozilla, being such a nice browser, allows the user to circumvent this.
However, when I right click a resource on such a page, I still get the
Javascript alert() call, followed by a fully functional context menu. Would it
be possible to make Mozilla skip the alert() call also?


Reproducible: Always

Steps to Reproduce:
1. Enable Javascript and forbid web pages from disabling the context menu.
2. Go to a page that disables the context menu.
3. Right click on a resource.

Actual Results:  
1. The page displays an alert whining about how saving resources is property
theft and so on.
2. I get full access to the Mozilla context menu.


Expected Results:  
Skip step 1 and go directly to step 2.
Hmm... it may indeed make sense to prevent alert() calls in oncontextmenu
handlers when we're overriding that stuff.  jst, thoughts?
I personally couldn't justify adding any code for this...
Version: unspecified → 1.7 Branch
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
==> DOM
Assignee: general → nobody
Product: Mozilla Application Suite → Core
QA Contact: general → general
Version: 1.7 Branch → Trunk
Assignee: nobody → general
Component: General → DOM
QA Contact: general → ian
Assignee: general → nobody
QA Contact: ian → general
Priority: -- → P5
Component: DOM → DOM: Core & HTML
Severity: trivial → S4
You need to log in before you can comment on or make changes to this bug.