Closed
Bug 1589962
Opened 5 years ago
Closed 5 years ago
Standalone mail window does not have gMessageBrowser defined
Categories
(SeaMonkey :: MailNews: Message Display, defect)
SeaMonkey
MailNews: Message Display
Tracking
(seamonkey2.49esr unaffected, seamonkey2.53 fixed, seamonkey2.57esr fixed)
RESOLVED
FIXED
seamonkey2.69
| Tracking | Status | |
|---|---|---|
| seamonkey2.49esr | --- | unaffected |
| seamonkey2.53 | --- | fixed |
| seamonkey2.57esr | --- | fixed |
People
(Reporter: iannbugzilla, Assigned: iannbugzilla)
Details
(Whiteboard: SM2.53.1)
Attachments
(1 file)
|
1.03 KB,
patch
|
frg
:
review+
frg
:
approval-comm-release+
frg
:
approval-comm-esr60+
|
Details | Diff | Splinter Review |
When opening an email message in a separate window, you get an error about gMessageBrowser not being defined.
[Approval Request Comment]
Regression caused by (bug #): Bug 654966
User impact if declined: Cannot save as template in standalone window
Testing completed (on m-c, etc.): 2.53
Risk to taking this patch (and alternatives if risky): None
String changes made by this patch: None
Attachment #9102832 -
Flags: review?(frgrahl)
Attachment #9102832 -
Flags: approval-comm-release?
Attachment #9102832 -
Flags: approval-comm-esr60?
|
||
Comment 2•5 years ago
|
||
Comment on attachment 9102832 [details] [diff] [review] Switch to getMessageBrowser LGTM
Attachment #9102832 -
Flags: review?(frgrahl)
Attachment #9102832 -
Flags: review+
Attachment #9102832 -
Flags: approval-comm-release?
Attachment #9102832 -
Flags: approval-comm-release+
Attachment #9102832 -
Flags: approval-comm-esr60?
Attachment #9102832 -
Flags: approval-comm-esr60+
Pushed by frgrahl@gmx.net:
https://hg.mozilla.org/comm-central/rev/962a739be4cb
Standalone mail window does not have gMessageBrowser defined. r=frg
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
|
|
||
Comment 4•5 years ago
|
||
status-seamonkey2.53:
--- → affected
status-seamonkey2.57esr:
--- → fixed
Target Milestone: --- → seamonkey2.69
|
|
||
Comment 5•4 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•