188861 - Improve localizing javascript bugs via View Source (display line numbers)

Status: RESOLVED DUPLICATE of bug 15364

(Core Graveyard :: View Source, defect)

Description

[Martin Hassman]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; cs-CZ; rv:1.3a) Gecko/20021212
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; cs-CZ; rv:1.3a) Gecko/20021212

Here is my idea, howto improve localizing javascript bugs in html (or js) source
via View Source and also improve cooperation with Javascript Console.

If someone find a javascript error message in js-console, there is a link to the
file with linenumber. You can click on this link and open View Source window
with code (html or js) in wich is error on line XX. But because in View Source
are not displayed line numbers and there is not any menuitem "Go to the line
number...", you can not simply look at the bug in detail. If is you js-code more
complex, you must calculate linenumbers or open this file in editor which has
this feature for displaying block of code with a bug.

Situation may be more simple if you add possibility to display line numbers at
left side of View Source window like in many plaintext editors. This may be
switched on/off via View Source menu.
Good job is also to create function go_to_linenumber(number) and add it to the
menu as "Go to the line..." item.

And very nice would be if you add posibility open file in View Source window at
some line number, so javascript bug localizing mamy be more simple, e.g. You
found error message in JavaScript Console, click on the link to the file with
error and this file is opened in View Source dialog and automatically scrolled
to the line with error. At the left side are visible linenumbers so complete
process take off only one second :-)

Reproducible: Always

Steps to Reproduce:

Comment 1

[Boris Zbarsky [:bzbarsky]]

See also bug 104383

*** This bug has been marked as a duplicate of 15364 ***