Gecko reports wrong fileName with exception when using legacy.js

[GoogleCodeExporter]

See the included testcase (Error.html). When using legacy.js, the
exception.fileName property (supported by Firefox only) is reported to be
legacy.js, instead of Error.html.

This might confuse developers, because the error reported (by firebug for
example) is claimed to be in legacy.js.

This probably also affects the window.onerror event. Within Gecko, the
fileName property is empty (see Error2.html). Within Internet Explorer, the
fileName is displayed.

Original issue reported on code.google.com by doek...@gmail.com on 23 May 2007 at 2:33

Attachments:

• Error.html
• Error2.html

[GoogleCodeExporter]

Fixed in trunk.

Original comment by dean.edw...@gmail.com on 19 Jun 2007 at 7:11

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Original comment by doek...@gmail.com on 14 Jul 2007 at 7:07

• Added labels: Browser-Mozilla, Module-base2
• Removed labels: ****