56799 - Javascript highlighting causes exceptions

Status: RESOLVED WORKSFORME

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

Description

[Reinout van Schouwen]

Go to the above URL and move mouse over menu options on the left.
The output I get is:

JavaScript error:
http://www.parool.nl/actueel/lunchnieuws/355023061.html line 22: can't convert
TimeoutID to an integer

JavaScript error:
 line 0: uncaught exception: [Exception... "Parameter is not a number"  code:
"1005" nsresult: "0x805303ed (NS_ERROR_DOM_NOT_NUMBER_ERR)"  location:
"http://www.parool.nl/actueel/lunchnieuws/355023061.html Line: 22"]

Comment 1

[Conor Lennon]

On a mouse over the following javascript is invoked (along with some other
javascript):

clearTimeout(TimeoutID);

As far as I can see the problem is that TimeoutID is not defined.
TimeoutID needs to be a number, and mozilla has difficulty in converting an
undefined variable to a number.  Hence the error.

Comment 2

[Phil Schwartau]

Conor is correct. The script defines TimeoutID, but doesn't initialize it.
Then it calls clearTimeout(TimoutID) :


<SCRIPT LANGUAGE="JavaScript">

   var js = !(((navigator.appName.toLowerCase()   etc. etc. 
   var TimeoutID;

   function mouseOver(name) {
     if (js) {
        clearTimeout(TimeoutID);
        buttonname = name;
        document.images[buttonname].src = "/nav/ov_" + buttonname + "_roll.gif";
     }
   }


You can produce the same error by typing this in the URL bar and hitting Enter: 

          javascript: var x; clearTimeout(x)


In Mozilla, you will see the reported errors in the JavaScript console. 
In NN4.7, I see no errors. By contrast, this produces no errors in Mozilla:


          javascript: var x=1; clearTimeout(x)


As to why the behavior differs between Mozilla and NN4.x, I will have
to defer to the DOM group. Reassigning to DOM Level 0. Is this bug valid?

Comment 3

[Asa Dotzler [:asa]]

setting bug status to New

Comment 4

[Johnny Stenback (:jst)]

Won't fix, the mozilla DOM doesn't accept unitialized variables as input,
unfortunately. The site needs to initialize TimeoutID to 0 before calling
clearTimeout().

WONTFIX.

Comment 5

[Phil Schwartau]

*** Bug 59605 has been marked as a duplicate of this bug. ***

Comment 6

[Fabian Guisset]

VERIFIED wontfix

Comment 7

[Johnny Stenback (:jst)]

Reopening, since this was actually fixed by the XPCDOM landing, so mozilla now
works as 4.x did.

Comment 8

[Johnny Stenback (:jst)]

Marking WORKSFORME since this was fixed a few weeks ago.