SeaMonkey 2.4 extension compatibility
Stanimir Stamenkov
SeaMonkey 2.3 and Firefox 7, but show some glitches with SeaMonkey
2.4, so I suspect there might be a SeaMonkey problem to that.
*Live HTTP Headers* 0.17 [1]
The request/response headers on the Page Info / Headers tab
appear empty (while the Headers in the Live HTTP Headers window are
shown o.k.).
There appear similar issues filled against Live HTTP Headers
0.16 for Firefox 4/SeaMonkey 2.1, but they appear o.k. with these
versions now:
https://www.mozdev.org/bugs/show_bug.cgi?id=23499
https://www.mozdev.org/bugs/show_bug.cgi?id=23502
*Open in Browser* 1.10 [2]
Open:
https://www.mozdev.org/bugs/show_bug.cgi?id=22167
Click on any of the image attachments. An "Opening..." dialog
is shown. Select "Open in browser as [_Image_]". Clicking "OK"
next appears to do nothing.
If you close the "Open with" dialog, next, then follow the
image attachment link again - it gets automatically opened in the
browser.
Do these issues appear to be SeaMonkey 2.4 problems or they just
need to be addressed by the extensions themselves?
[1] https://addons.mozilla.org/addon/live-http-headers/
[2] https://addons.mozilla.org/addon/open-in-browser/
--
Stanimir
Stanimir Stamenkov
problems with the following extensions using:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0) Gecko/20110826 Firefox/7.0
SeaMonkey/2.4
Sat, 23 Jul 2011 19:04:59 +0300, /Stanimir Stamenkov/:
> There are few extensions which appear to work just fine with SeaMonkey
> 2.3 and Firefox 7, but show some glitches with SeaMonkey 2.4, so I
> suspect there might be a SeaMonkey problem to that.
>
> *Live HTTP Headers* 0.17 [1]
>
> The request/response headers on the Page Info / Headers tab appear empty
> (while the Headers in the Live HTTP Headers window are shown o.k.).
>
> There appear similar issues filled against Live HTTP Headers 0.16 for
> Firefox 4/SeaMonkey 2.1, but they appear o.k. with these versions now:
>
> https://www.mozdev.org/bugs/show_bug.cgi?id=23499
> https://www.mozdev.org/bugs/show_bug.cgi?id=23502
Looking at the Error Console I observe the following errors appear when
I open the Page Info:
Error: Services is not defined
Source File: chrome://navigator/content/pageinfo/permissions.js
Line: 38
Error: uncaught exception: [Exception... "Component returned failure
code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE)
[nsIObserverService.addObserver]" nsresult: "0x80070057
(NS_ERROR_ILLEGAL_VALUE)" location: "JS frame ::
chrome://navigator/content/pageinfo/permissions.js :: onLoadPermission
:: line 101" data: no]
FWIW, I get the same in Safe Mode, also. Bug 662107
<https://bugzilla.mozilla.org/show_bug.cgi?id=662107> appears related.
> *Open in Browser* 1.10 [2]
>
> Open:
>
> https://www.mozdev.org/bugs/show_bug.cgi?id=22167
>
> Click on any of the image attachments. An "Opening..." dialog is shown.
> Select "Open in browser as [_Image_]". Clicking "OK" next appears to do
> nothing.
>
> If you close the "Open with" dialog, next, then follow the image
> attachment link again - it gets automatically opened in the browser.
>
> Do these issues appear to be SeaMonkey 2.4 problems or they just need to
> be addressed by the extensions themselves?
>
> [1] https://addons.mozilla.org/addon/live-http-headers/
> [2] https://addons.mozilla.org/addon/open-in-browser/
Using Open in Browser 1.11 now, I see in the Error Console:
Error: Application.activeWindow is undefined
Source File: chrome://openinbrowser/content/openInBrowser.js
Line: 139
Was 'Application.activeWindow' removed after SeaMonkey 2.3?
--
Stanimir
Philip Chee
> Looking at the Error Console I observe the following errors appear when
> I open the Page Info:
>
> Error: Services is not defined
> Source File: chrome://navigator/content/pageinfo/permissions.js
> Line: 38
>
> Error: uncaught exception: [Exception... "Component returned failure
> code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE)
> [nsIObserverService.addObserver]" nsresult: "0x80070057
> (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame ::
> chrome://navigator/content/pageinfo/permissions.js :: onLoadPermission
> :: line 101" data: no]
>
> FWIW, I get the same in Safe Mode, also. Bug 662107
> <https://bugzilla.mozilla.org/show_bug.cgi?id=662107> appears related.
If you click on the "Depends on" link on that bug you'll get:
https://bugzilla.mozilla.org/show_bug.cgi?id=675858
Hint: [good first bug]
> Using Open in Browser 1.11 now, I see in the Error Console:
>
> Error: Application.activeWindow is undefined
> Source File: chrome://openinbrowser/content/openInBrowser.js
> Line: 139
>
> Was 'Application.activeWindow' removed after SeaMonkey 2.3?
Aaargh. We need to port the relevant parts of:
Bug 658632 (Provide easy way to add non-leaky classinfo to JS components)
Please file a bug and CC me.
Phil
--
Philip Chee <phi...@aleytys.pc.my>, <phili...@gmail.com>
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
Stanimir Stamenkov
> On Sat, 27 Aug 2011 19:37:03 +0300, Stanimir Stamenkov wrote:
>
>> Using Open in Browser 1.11 now, I see in the Error Console:
>>
>> Error: Application.activeWindow is undefined
>> Source File: chrome://openinbrowser/content/openInBrowser.js
>> Line: 139
>>
>> Was 'Application.activeWindow' removed after SeaMonkey 2.3?
>
> Aaargh. We need to port the relevant parts of:
>
> Bug 658632 (Provide easy way to add non-leaky classinfo to JS components)
>
> Please file a bug and CC me.
https://bugzilla.mozilla.org/show_bug.cgi?id=682587
--
Stanimir
Justin Wood (Callek)
Thanks for the report, and to Ratty for catching which bug this was
caused from.
I'll work on it asap, and try and drive it forward despite the (slight)
API changes this entails. This late in the game, I can't promise it will
be accepted for SeaMonkey 2.4, but given its impact I hope we can take it.
--
~Justin Wood (Callek)