864680 - some js syntax errors won't report through debugger

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[Jim Michaels]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0
Build ID: 20130409194949

Steps to reproduce:

I didn't think I was doing anything spectacular. at most I use onchange= and onkeyup= and a lot of functions. I mess up a lot on my syntax because my typing seems to have gotten bad in my 40's (or maybe it was because of typing for years at 45 degrees).
dw cs5 shows no js syntax errors. but code is dead. here is a current snapshot of the files. you shouldn't have to click any buttons to get results:

http://Jesusnjim.com/test/broken-js-syntax-prevents-debugger-from-showing-errors.html




Actual results:

no good results from sample values, probably due to odd syntax error. firebug debugger did not mention any errors. this happens a lot to me with firefox. syntax gets bad in a way that debugger will not report any errors. then you have to debug all by yourself, manually. I have a LOT of code to pour through, so I don't take this lightly. apparently js engine just gives up and says everything is fine when it's not. does same thing in chrome, ... oohh. I found some bugs in ff too by opening this page up in opera and using its dragonfly debugger and clicking on the errors button (shows 224, 2 are interesting). will report in a different bug report.


Expected results:

js engine should report any and all script syntax errors through debugger.

Comment 1

[Jim Michaels]

changed title to more accurately reflect situation

Comment 2

[Jim Michaels]

might be caused by undefined functions or variables in my client code. these seem to report fine through ff debugger though. interesting. could be firebug problem. they don't know how to fix when something is undefined except to go back up the call stack when there's an exception and see what happened - but no error reported, does nothing, seems like in that instance, javascript plays dead and firebug debugger says everything's great.

I am *beginning* to think this is a firebug issue ONLY, after seeing the ff debugger for the first time in action.

Comment 3

[Maria Grazia Alastra [:mga]]

Hello, if you have an issue specifically with Firebug you may want to report it in the following page: https://code.google.com/p/fbug/issues/list

Thank you :)

Comment 4

[Sebastian Zartner [:sebo]]

The bug description is very vague and the provided test page doesn't have any syntax errors (tested in all major browsers).
If you have a specific problem, please break it down to a simple, reproducible test case including precise steps. The Firebug wiki has a good description of how to create a good test case.[1]
If you have this test case, please report a new issue.

Sebastian

[1] https://getfirebug.com/wiki/index.php/Creating_a_Test_Case