Closed
Bug 482181
Opened 17 years ago
Closed 17 years ago
Stop dumping expected conditions in MsgComposeCommands
Categories
(Thunderbird :: Message Compose Window, defect)
Thunderbird
Message Compose Window
Tracking
(Not tracked)
RESOLVED
FIXED
Thunderbird 3.0b3
People
(Reporter: philor, Assigned: philor)
Details
Attachments
(1 file)
|
5.28 KB,
patch
|
Bienvenu
:
review+
|
Details | Diff | Splinter Review |
In May 1999, putterman landed version 1.1 of MsgComposeCommands.js, which included things like "dump("SendMessage from JS!\n");" which at the time probably deserved the exclamation point, if not the dump().
In June 1999, ducarroz changed that to "dump("SendMessage from XUL\n");" apparently already finding it a bit less exciting.
For the next 9.75 years, every time someone with .dump.enabled has sent a message we've spewed about
SendMessage from XUL
GenericSendMessage from XUL
Identity = [nsIMsgIdentity: id1]
and I think being amazed that we can call one function and have it call another function for more than 10 years would just be too much, as is assuming that everyone wants to debug GetArgs and DetermineHTMLAction every time they write email.
Attachment #366254 -
Flags: review?(bienvenu)
Updated•17 years ago
|
Attachment #366254 -
Flags: review?(bienvenu) → review+
| Assignee | ||
Comment 1•17 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•17 years ago
|
Flags: in-testsuite-
You need to log in
before you can comment on or make changes to this bug.
Description
•