186351 - Javascript: "is not a registred protocol"

Status: RESOLVED INVALID

(Core :: DOM: Events, defect)

Description

[philippe]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021210
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021210

I've a html generated page by JavaScript.
In IE6 it works fine.

Amongst the JS code, the code states that on mouse event on a hyperlink, a
javascript alert ought to prompt which mouse button was press.
Generated statement looks as this:
<a HREF="" onMouseDown="extLinks(event.button,'Atest');return false">Atest</a>

Some how Mozilla states in the alert box "is not a registred protocol".

However, if I copy and paste the generated hmtl page in a file and open the
directly the file, Mozilla is correctly working.

The code being far too long to give, how can I follow the JS excution of Mozilla
in order to identifying the underlying bug in Mozilla?

Yours

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Joel Peshkin]

-->browser

Comment 2

[Dave Miller [:justdave]]

fixing owner/qa

Comment 3

[Phil Schwartau]

---> DOM Events

If that mousedown handler ever gets called, I don't see how it
could ever work in Mozilla, because the |event| object is IE-only:

       onMouseDown="extLinks(event.button,'Atest');

Does the page custom-define its own object called "event"?

Comment 4

[Vladimir Ermakov]

Um, doubt it's dom events, but I cant judge anything without a testcase. Please
provide a link to the site, or event better, attach a minimised testcase.

Comment 5

[Henrik Lynggaard Hansen]

As stated in comment 3, event is IE-specific I'm tempted at closing this bug as
invalid, esp. given the lack of response from the reporter.

Reporter,could you please try and provide what is suggested in comment 4 and/or
- The definition of this event object ?
- the code for the eventHandler ?

Comment 6

[Gérard Talbot]

There is nothing to be done without an URL, a page, explicit+clear steps to
reproduce or best, a reduced testcase. After a whole year of waiting from the
reporter on this, I'm RESOLVING this bug as INVALID.