1280158 - mishandling of commented out curly braces in debugger?

Status: RESOLVED WONTFIX

(DevTools :: Debugger, defect)

Description

[Jim Michaels]

User Agent: Mozilla/5.0 (Windows NT 6.0; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID: 20160604131506

Steps to reproduce:

http://Jesusnjim.com/index.html_
yes, the _ is part of the path.
SyntaxError: missing } after function body DTime.js:2787:0
ReferenceError: StringToDTime is not defined
GetDeadlineDatestring()
 index.html_:350
updateXPEOL()
 index.html_:483
<anonymous>
 index.html_:520
 index.html_:350:6



Actual results:

that } is the last char in the file DTime.js. so I suspect there are too many opens, but the debugger is not telling me that.


Expected results:

better error message, and more accurate. the curly brace is there. something is throwing off the debugger, and it's big code.

Comment 1

[Eddy Bruel [:ejpbruel]]

(In reply to Jim Michaels from comment #0)
> User Agent: Mozilla/5.0 (Windows NT 6.0; rv:47.0) Gecko/20100101 Firefox/47.0
> Build ID: 20160604131506
> 
> Steps to reproduce:
> 
> http://Jesusnjim.com/index.html_
> yes, the _ is part of the path.
> SyntaxError: missing } after function body DTime.js:2787:0
> ReferenceError: StringToDTime is not defined
> GetDeadlineDatestring()
>  index.html_:350
> updateXPEOL()
>  index.html_:483
> <anonymous>
>  index.html_:520
>  index.html_:350:6
> 
> 
> 
> Actual results:
> 
> that } is the last char in the file DTime.js. so I suspect there are too
> many opens, but the debugger is not telling me that.
> 
> 
> Expected results:
> 
> better error message, and more accurate. the curly brace is there. something
> is throwing off the debugger, and it's big code.

Hi Jim.

I took a look at the error you're getting. The error is reported by the console, which means that its not coming from the debugger, but from the JavaScript engine itself.

I agree that 'missing }' is not a particularly helpful error message. I would love for us to improve on that, but that's a JavaScript engine problem, not a debugger problem. Moreover, this is generally very hard to do, because parsers have a hard time figuring out what you actually meant to do.

Since this is not a debugger bug, I'm going to have to close this particular bug as wontfix.

Thanks for your bug report!