It's very nice what it does right now. But wouldn't it be much better if when you click on the error it took you to the proper source file line and highlighted it? Now it opens the source file but it's difficult to find the error whithout saving the source to a file and doing "vi +198 source.js".

-> XP apps

See bug 15364 At the moment, there is really no good way to find the right line in view source... But this would be a really good idea, yes.

I imagine something like this (I know very little about the inner workings of mozilla, sorry): The JavaScript console points to an URL like... view-source:[.......]?line=N . Where such an URL is followed, a "view source" windows is opened which scrolls to the given line and highlits it. If the users clicks (or select with the keyboard) on another error which points to the same file, that error should be highlited in the previously opened view-source window. This way the user will be able to easily inspect all the errors which occured in a page just with the "up" and "down" keys. Just some ideas... sorry for disturbing the bugzilla peace.. (!) bye!

> The JavaScript console points to an URL like... view-source:[.......]?line=N . > Where such an URL is followed, a "view source" windows is opened which scrolls > to the given line and highlits it. That's exactly what I'd like to do once view source counts lines correctly. :) As for the other, that would indeed be cool. I'll try to think of a way to do it, but I'm really not sure how to approach it...

is this bug really js console? the js console is doing the right thing. It's just the view-source window that doesn't support linenumber and highlight. seems like a dupe of bug 79612

bug 79612 scrolls to the line, this bug highlits it. But the line can't be highlited if the windows doesn't scroll. So I'd say that bug 79612 blocks this one.. =)

This is up to the view-source window, not the javascript console.

view source --> doron

Clicking on a link in the JS console now highlights the line of the error or warning. Looks like this bug is WFM.

Yeah, this got fixed when bug 104383 got fixed.