Click event via dispatchEvent stops working in Firefox 1.0 Gecko/20041107

RESOLVED WONTFIX

Status

()

Core
DOM: Events
RESOLVED WONTFIX
14 years ago
14 years ago

People

(Reporter: John Spurlock, Unassigned)

Tracking

({regression, testcase})

Trunk
x86
Windows XP
regression, testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

See the attached testcase (the "fake" scripting links should behave similarly to
the normal links)

The click event is correctly dispatched in mozilla 1.7.3 (Gecko/20040910) and 
firefox 0.9.3 (Gecko/20040803) and had been working in release candidates of
firefox 1.0

Now, neither case works - is this a known issue?  Thought it might be the
popup-blocker, but doesn't seem to make a difference.





Reproducible: Always
Steps to Reproduce:
1.
2.
3.
(Reporter)

Comment 1

14 years ago
Created attachment 165930 [details]
Testcase

Comment 2

14 years ago
Confirmed.

This scenario was one of my tests for the new popup blocker, so the bug must've
been introduced later...
Status: UNCONFIRMED → NEW
Ever confirmed: true

Updated

14 years ago
Keywords: regression, testcase
This was done intentionally in bug 265176.
Yes, this is intentional, marking WONTFIX.
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 5

14 years ago
(In reply to comment #4)
> Yes, this is intentional, marking WONTFIX.

Ok, so going forward, this will no longer be allowed?  What's the rationale?

Specifically, which gecko builds will this affect?  Is there another way to
launch a link via scripting for these affected versions?





Comment 6

14 years ago
Bug 265176 is a security issue, that why is cannot be accessed. That means that
we won't get a rationale until after Mozilla 1.8 is released. The versions
"affected" are Firefox starting with 1.0 and Mozilla starting with 1.8a5. And it
is easy enough to trigger a link:

window.location.href = link.href;
also affected will be mozilla starting 1.7.4 or .5
(Reporter)

Comment 8

14 years ago
fair enough, thanks for the explanation
You need to log in before you can comment on or make changes to this bug.