Closed
Bug 275338
Opened 20 years ago
Closed 12 years ago
dispatching a "click" event on a <a> link doesn't navigate to the target page anymore
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: henning.pingel, Unassigned)
Details
Attachments
(1 file, 1 obsolete file)
|
945 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.2) Gecko/20040803 Mnenhy/0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5) Gecko/20041108 Firefox/1.0 The javascript within the provided example-html-page simulates a click on a link in this page through javascript. This brings up an alert box at page onLoad. It works within the following tested browser releases: 1) Mozilla 1.4 2) Mozilla 1.7.2 3) Firefox Preview Release 1.0 (Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10) It does not work within: 1) Firefox 10rc1 2) Firefox 10rc2 3) Firefox 1.0 Nothing happens here and no javascript error is displayed within the console. The same problem was discussed by others here: http://groups.google.de/groups?hl=de&lr=&selm=a75eeba1.0411201754.41b80460%40posting.google.com Reproducible: Always Steps to Reproduce: Display the attached html page. Actual Results: If the error occurs there should not be a javascript alert box coming up automatically. Expected Results: Because there is a body onLoad event the function click should have opened an js alert box.
| Reporter | ||
Comment 1•20 years ago
|
||
| Reporter | ||
Comment 2•20 years ago
|
||
Error also occurs in Mozilla 1.7.5.
Comment 3•20 years ago
|
||
Requesting blocking since this is causing me problems with my rewrite of the Image Toolbar extension.
Flags: blocking-aviary1.1?
Comment 4•20 years ago
|
||
As Neil said in the referenced newsgroup thread: "the navigation may have been disabled because of concerns about popup blocking. If you just want to ensure the navigation occurs you can of course use window.location = linkElement.href;" The event handling part is okay, as you can see from updated testcase.
Attachment #169172 -
Attachment is obsolete: true
Comment 5•20 years ago
|
||
updating summary, my build is Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050412 Firefox/1.0+ please confirm/deny that *this* is your true problem.
Summary: javascript: createEvent / initMouseEvent / dispatchEvent doesn't work any more → dispatching a "click" event on a <a> link doesn't navigate to the target page any more
Comment 6•20 years ago
|
||
Apologies, you're right that this is not my issue... I guess the bad summary caught me out. Your new testcase WFM, so I'll figure out what's going on and post that to the forum thread. Thanks.
Flags: blocking-aviary1.1?
Comment 7•20 years ago
|
||
Note that it's still interesting to know whether it's a regression on my testcase.
Summary: dispatching a "click" event on a <a> link doesn't navigate to the target page any more → dispatching a "click" event on a <a> link doesn't navigate to the target page anymore
Version: unspecified → Trunk
Updated•18 years ago
|
Assignee: bross2 → nobody
Comment 8•17 years ago
|
||
bug 265176 was the actual reference caused this right? I wonder if we can have a workaround for XUL apps.
Comment 9•12 years ago
|
||
updated testcase worksforme in the latest Firefox nightly build.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•