Closed
Bug 1640625
Opened 4 years ago
Closed 4 years ago
Fix globalmessagemanager following landing of Bug 888600
Categories
(SeaMonkey :: General, defect)
SeaMonkey
General
Tracking
(seamonkey2.53+ fixed, seamonkey2.57esr? affected)
RESOLVED
FIXED
seamonkey 2.75
People
(Reporter: iannbugzilla, Assigned: iannbugzilla)
Details
(Whiteboard: SM2.53.3)
Attachments
(1 file)
1.33 KB,
patch
|
frg
:
review+
frg
:
approval-comm-release+
frg
:
approval-comm-esr60+
|
Details | Diff | Splinter Review |
In Bug 888600 ContentFrameMessageManager was moved to WebIDL, we need to fix our one use of globalmessagemanager in nsSuiteGlue.js (see part 6 of bug - https://hg.mozilla.org/mozilla-central/rev/243246b2f440)
Needed where Bug 888600 has landed.
Attachment #9151524 -
Flags: review?(frgrahl)
Attachment #9151524 -
Flags: approval-comm-esr60?
Comment 2•4 years ago
|
||
Comment on attachment 9151524 [details] [diff] [review] Port loadFrameScript fix Can probably go into all current trees.
Attachment #9151524 -
Flags: review?(frgrahl)
Attachment #9151524 -
Flags: review+
Attachment #9151524 -
Flags: approval-comm-release+
Attachment #9151524 -
Flags: approval-comm-esr60?
Attachment #9151524 -
Flags: approval-comm-esr60+
Pushed by frgrahl@gmx.net:
https://hg.mozilla.org/comm-central/rev/1317619f493e
Fix globalmessagemanager following landing of Bug 888600. r=frg
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Comment 4•4 years ago
|
||
Landed with a reformat of the call as discussed on irc.
The Services call is available for 2.53 and 2.57 so can be taken there safely to align the source with central.
status-seamonkey2.53:
--- → affected
status-seamonkey2.57esr:
--- → affected
tracking-seamonkey2.53:
--- → ?
tracking-seamonkey2.57esr:
--- → ?
Target Milestone: --- → seamonkey 2.75
Comment 5•4 years ago
|
||
Target 2.53.3
https://gitlab.com/seamonkey-project/seamonkey-2.53-comm/-/commit/8072116cebd4477cec6c03f8ac3935eb289e5fdc
Fix globalmessagemanager following landing of Bug 888600. r=frg a=frg
You need to log in
before you can comment on or make changes to this bug.
Description
•