351667 - Would like a timestamp for all errors/messages/exceptions

Status: RESOLVED DUPLICATE of bug 122213

(Toolkit Graveyard :: Error Console, enhancement)

Description

[Håkan Waara]

Just like in the system console, a timestamp would be very useful. 

Especially if you're bringing up the console after the fact (e.g., you've been running Firefox for 10 minutes, and want to be able to separate errors that happened 8 mins ago and just now).

Comment 1

[Ryan Jones-Ward [:sciguyryan]]

Looks like this is probably a dupe of bug #122213 - "Error Console should also include time and date the error occurred".

If you don't think this is a duplicate, cna someone please re-mark the bug.

- Ryan

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

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

Comment 2

[:Gavin Sharp [email: [e-mail]]]

That's an old bug that's in a component that doesn't apply to Firefox.

Comment 3

[:Gijs (he/him)]

Why was this marked deps on the console service redesign bug? Surely if the system console can do it, then the js console can too? I'd imagine it'll do perfectly fine to simply get a timestamp (var ts = new Date()) when the message gets logged to the console (which, I'd imagine, is simply done by a listener the js console has attached to the console service... right?)

Comment 4

[Simon Bünzli]

(In reply to comment #3)
> Why was this marked deps on the console service redesign bug?

From comment #0: "bringing up the console after the fact".

AFAICT there are two ways of achieving the goal of this bug:
1. Get the information directly from the console service (requires bug 228205 to be fixed).
2. Create an XPCOM component which logs all errors including the timestamp and get the errors from that component for the Error Console.

Solution #2 can at best be considered a (not too ugly - but nonetheless) hack, thus the dependency on bug 228205.

Comment 5

[Serge Gautherie (:sgautherie)]

(In reply to comment #2)
> That's an old bug that's in a component that doesn't apply to Firefox.

Could you double-check that ?
AFAICT, these bugs are duplicates.

Comment 6

[Philip Chee]

>> That's an old bug that's in a component that doesn't apply to Firefox.
> Could you double-check that ?
> AFAICT, these bugs are duplicates.

Originally they weren't in that Core::Error Console is/was the XPFE version and Firefox::Error Console is the toolkit version. However SeaMonkey trunk is now using the toolkit Error Console and the XPFE Error Console is unused except for branch.

See: http://www.gerv.net/temp/bmo-reorg.html

Comment 7

[Serge Gautherie (:sgautherie)]

(In reply to comment #6)

Agreeing on history.