120680 - the arrow that shows where the error is is sometimes in a wrong place (using backslashes)

Status: RESOLVED WORKSFORME

(Toolkit Graveyard :: Error Console, defect)

Description

[Julien Wajsberg [:julienw]]

When there is an error, the arrow soemtimes shows incorrectly. I think it's
especially related when there are some backslashes (\) in the javascript code
showed.

Reproducibility : every time

Steps to reproduce :
1.Open the URL mentioned
2.Open Javascript Console
3.Click Clear to remove all older errors
4.Click on bad1 bad2 bad3 bad4
5.Look in the Javascript Console

Actual results :
With Mozilla Linux, the error is badly reported (arrow is under the bad caracter)
With Mozilla Windows, the error is badly reported only with bad4.

Expected results :
The arrow should be under the faulty '.

Comment 1

[Julien Wajsberg [:julienw]]

Attachment: testcase

Comment 2

[Julien Cegarra]

Confirmed. (Build ID: 2002 01 21 03/Win98).

/jc

Comment 3

[John Levon]

Duping to a bug that got some attention.

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

Comment 4

[Julien Wajsberg [:julienw]]

I don't think it's the same bug, since the Javascript Console correctly shows
where the error is most of the time, although it uses a scaled font.

Comment 5

[Kai Lahmann (is there, where MNG is)]

I can see it here (2002073022, Linux), so this is at least a real bug (and not
that dup)

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 7

[Philip Chee]

Confirm that the problem still exists on:
Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9.1pre) Gecko/20090614 SeaMonkey/2.0b1pre

In addition all four errors are problematic on WinXP rather than only bad4 as described in Comment 0

Comment 8

[Nochum Sossonko [:Natch]]

This should be fixed by the patch in bug 305206, setting dependency.

Comment 9

[Julien Wajsberg [:julienw]]

The newer WebConsole doesn't show anymore where there is an error. I don't know if I should call this a win, but at least this makes this bug INVALID, I guess ?

Comment 10

[Philip Chee]

(In reply to Julien Wajsberg [:julienw] from comment #9)
> The newer WebConsole doesn't show anymore where there is an error. I don't
> know if I should call this a win, but at least this makes this bug INVALID,
> I guess ?
This bug isn't invalid because this bug is about the Toolkit Error Console, not the Devtools Web Console. And the TK Error Console is used by other applications like Thunderbird, SeaMonkey, and Instantbird - all of which live in the comm-central repository.

Comment 11

[Brian Grinstead [:bgrins]]

The Error Console has been removed in favor of the Browser Console (see Bug 1278368), and the component is going to be removed.  If this bug is also relevant in the Browser Console, please reopen and move this into Firefox -> Developer Tools: Console.

Comment 12

[Zack Weinberg (:zwol)]

I am mass-reopening and re-componenting every single one of the Toolkit:Error Console bugs that appear to have been closed without anyone even *glancing* at whether they were relevant to the Browser Console.

If you want to close a whole bunch of old bugs -- FOR ANY REASON -- it is YOUR RESPONSIBILITY to check EVERY SINGLE ONE OF THEM and make sure they are no longer valid.  Do not push that work onto the bug reporters.

(It's okay to close bugs that haven't been touched in years when they don't have enough information for you to figure out whether the problem is still relevant to the current software - the reporter probably isn't coming back to clarify.  But that is the ONLY situation where it is okay.)

(I'm going to have to do this in two steps because of the way the "change several bugs at once" form works.  Apologies for the extra bugspam.)

Comment 13

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

SyntaxError: missing ) after argument list
I think this qualifies as WFM.