Re: Extensions, 2.49.2

[Allen]

EE wrote:

WaltS48 wrote:

On 2/24/18 3:27 PM, Allen wrote:
I'm now running Seamonkey 2.49.2.  I don't find may extensions that 
are compatible with it, though.  Any general information about the 
timeline for the popular extensions?  My favorites are uBlock Origin 
and NoScript.



Install this extension to find extensions.

https://addons.mozilla.org/en-US/seamonkey/addon/amo-browsing-for-seamonkey/ 




This is where you can get uBlock Origin:
https://github.com/gorhill/uBlock/releases
Get the one called "uBlock0.firefox.xpi".

 I installed the latest non-beta version and it seems to work.  Thanks!

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions, 2.49.2

[EE]

WaltS48 wrote:

On 2/24/18 3:27 PM, Allen wrote:
I'm now running Seamonkey 2.49.2.  I don't find may extensions that 
are compatible with it, though.  Any general information about the 
timeline for the popular extensions?  My favorites are uBlock Origin 
and NoScript.



Install this extension to find extensions.

https://addons.mozilla.org/en-US/seamonkey/addon/amo-browsing-for-seamonkey/ 




This is where you can get uBlock Origin:
https://github.com/gorhill/uBlock/releases
Get the one called "uBlock0.firefox.xpi".
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions, 2.49.2

[WaltS48]

On 2/24/18 3:27 PM, Allen wrote:
I'm now running Seamonkey 2.49.2.  I don't find may extensions that 
are compatible with it, though.  Any general information about the 
timeline for the popular extensions?  My favorites are uBlock Origin 
and NoScript.



Install this extension to find extensions.

https://addons.mozilla.org/en-US/seamonkey/addon/amo-browsing-for-seamonkey/

--
Best name ever! Cadet Bone Spurs
Coexist
National Popular Vote
Ubuntu 16.04LTS - Unity Desktop

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions

[Philip Chee]

On 08/11/2013 02:04, JAS wrote:

>> em:targetApplication>
>>   
>> 
>> {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
>> 2.22
>> 2.22.*
>>   
>> 
>>
> How do you know the em:id ?

https://addons.mozilla.org/en-US/seamonkey/pages/appversions/

Phil

-- 
Philip Chee , 
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.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions

[JAS]

EE wrote:
> JAS wrote:
>> WaltS wrote:
>>> On 11/07/2013 11:37 AM, Ed Mullen wrote:
 Someone asked me what prevents some Firefox (and Tbird) extensions
 from
 being used in SeaMonkey.

 I know that the UI differences can be an issue but how about other
 technical "stuff"?

>>>
>>>
>>>
>>> I believe it needs this whole SeaMonkey section of code in the
>>> install.rdf file. Example from Lightning 2.7b1 for SeaMonkey 2.22.
>>>
>>> em:targetApplication>
>>>
>>>  
>>>  {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
>>>  2.22
>>>  2.22.*
>>>
>>>  
>>>
>> How do you know the em:id ?
>>
> Copy it from something that will install only in SeaMonkey; for
> instance, a SeaMonkey theme.
>
Thanks to everyone for the replies and the links, I think I have it now.

-- 
   You either teach people to treat you with dignity and respect, or you don't. 
This means you are partly responsible for the mistreatment that you get at the 
hands of someone else. 

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions

[EE]

JAS wrote:

WaltS wrote:

On 11/07/2013 11:37 AM, Ed Mullen wrote:

Someone asked me what prevents some Firefox (and Tbird) extensions from
being used in SeaMonkey.

I know that the UI differences can be an issue but how about other
technical "stuff"?





I believe it needs this whole SeaMonkey section of code in the
install.rdf file. Example from Lightning 2.7b1 for SeaMonkey 2.22.

em:targetApplication>
   
 
 {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
 2.22
 2.22.*
   
 


How do you know the em:id ?

Copy it from something that will install only in SeaMonkey; for 
instance, a SeaMonkey theme.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions

[EE]

Ed Mullen wrote:

Someone asked me what prevents some Firefox (and Tbird) extensions from
being used in SeaMonkey.

I know that the UI differences can be an issue but how about other
technical "stuff"?

One must have the correct items in the chrome.manifest in the installer. 
 For instance, Firefox has browser.xul, whereas SeaMonkey has 
navigator.xul instead.  The correct ID number for the application must 
be in the install.rdf file.  These are different between Firefox, 
SeaMonkey and Thunderbird.  The correct max and min version numbers must 
also be present.


If you get these correct, there is still no guarantee that the extension 
will work properly and will not screw up something.  Some extensions 
when modified to install into SeaMonkey will work, and some will not.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions

[WaltS]

On 11/07/2013 01:04 PM, JAS wrote:

WaltS wrote:

On 11/07/2013 11:37 AM, Ed Mullen wrote:

Someone asked me what prevents some Firefox (and Tbird) extensions from
being used in SeaMonkey.

I know that the UI differences can be an issue but how about other
technical "stuff"?





I believe it needs this whole SeaMonkey section of code in the
install.rdf file. Example from Lightning 2.7b1 for SeaMonkey 2.22.

em:targetApplication>
   
 
 {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
 2.22
 2.22.*
   
 


How do you know the em:id ?




How do I or an extension developer know it?

I copied the code from a install.rdf file.

One reference for extension developers can be found here.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions

[WaltS]

On 11/07/2013 12:59 PM, regz91 wrote:

WaltS wrote:

On 11/07/2013 11:37 AM, Ed Mullen wrote:

Someone asked me what prevents some Firefox (and Tbird) extensions from
being used in SeaMonkey.

I know that the UI differences can be an issue but how about other
technical "stuff"?





I believe it needs this whole SeaMonkey section of code in the
install.rdf file. Example from Lightning 2.7b1 for SeaMonkey 2.22.

em:targetApplication>
   
 
 {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
 2.22
 2.22.*
   
 


In addition to install.rdf you need to make relevant changes in
install.js too.

Here is a complete guide
https://developer.mozilla.org/en-US/docs/Extensions_support_in_SeaMonkey_2




Your complete guide has this statement.

[quote]
The install.js is not supported any more and should be removed.
[/quote]
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions

[regz91]

JAS wrote:

WaltS wrote:

On 11/07/2013 11:37 AM, Ed Mullen wrote:

Someone asked me what prevents some Firefox (and Tbird) extensions from
being used in SeaMonkey.

I know that the UI differences can be an issue but how about other
technical "stuff"?





I believe it needs this whole SeaMonkey section of code in the
install.rdf file. Example from Lightning 2.7b1 for SeaMonkey 2.22.

em:targetApplication>
   
 
 {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
 2.22
 2.22.*
   
 


How do you know the em:id ?

write up on em:id :- 
https://developer.mozilla.org/en-US/docs/Install_Manifests#Required_Property_Reference


--
GNOME 3.6.2
openSUSE Release 12.3 (Dartmouth) 64-bit
Kernel Linux 3.7.10-1.16-desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions

[regz91]

regz91 wrote:

WaltS wrote:

On 11/07/2013 11:37 AM, Ed Mullen wrote:

Someone asked me what prevents some Firefox (and Tbird) extensions from
being used in SeaMonkey.

I know that the UI differences can be an issue but how about other
technical "stuff"?





I believe it needs this whole SeaMonkey section of code in the
install.rdf file. Example from Lightning 2.7b1 for SeaMonkey 2.22.

em:targetApplication>
   
 
 {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
 2.22
 2.22.*
   
 


In addition to install.rdf you need to make relevant changes in
install.js too.

Here is a complete guide
https://developer.mozilla.org/en-US/docs/Extensions_support_in_SeaMonkey_2


correction "install.js" should be "chrome.manifest"

--
GNOME 3.6.2
openSUSE Release 12.3 (Dartmouth) 64-bit
Kernel Linux 3.7.10-1.16-desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions

[JAS]

WaltS wrote:
> On 11/07/2013 11:37 AM, Ed Mullen wrote:
>> Someone asked me what prevents some Firefox (and Tbird) extensions from
>> being used in SeaMonkey.
>>
>> I know that the UI differences can be an issue but how about other
>> technical "stuff"?
>>
>
>
>
> I believe it needs this whole SeaMonkey section of code in the
> install.rdf file. Example from Lightning 2.7b1 for SeaMonkey 2.22.
>
> em:targetApplication>
>   
> 
> {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
> 2.22
> 2.22.*
>   
> 
>
How do you know the em:id ?

-- 
   You either teach people to treat you with dignity and respect, or you don't. 
This means you are partly responsible for the mistreatment that you get at the 
hands of someone else. 

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions

[regz91]

WaltS wrote:

On 11/07/2013 11:37 AM, Ed Mullen wrote:

Someone asked me what prevents some Firefox (and Tbird) extensions from
being used in SeaMonkey.

I know that the UI differences can be an issue but how about other
technical "stuff"?





I believe it needs this whole SeaMonkey section of code in the
install.rdf file. Example from Lightning 2.7b1 for SeaMonkey 2.22.

em:targetApplication>
   
 
 {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
 2.22
 2.22.*
   
 

In addition to install.rdf you need to make relevant changes in 
install.js too.


Here is a complete guide 
https://developer.mozilla.org/en-US/docs/Extensions_support_in_SeaMonkey_2


--
GNOME 3.6.2
openSUSE Release 12.3 (Dartmouth) 64-bit
Kernel Linux 3.7.10-1.16-desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions

[WaltS]

On 11/07/2013 11:37 AM, Ed Mullen wrote:

Someone asked me what prevents some Firefox (and Tbird) extensions from
being used in SeaMonkey.

I know that the UI differences can be an issue but how about other
technical "stuff"?





I believe it needs this whole SeaMonkey section of code in the 
install.rdf file. Example from Lightning 2.7b1 for SeaMonkey 2.22.


em:targetApplication>
  

{92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
2.22
2.22.*
  


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions As Bug Work-Arounds

[Rufus]

MCBastos wrote:

Interviewed by CNN on 17/03/2012 20:29, David E. Ross told the world:


And, no, extensions are not sufficient to solve a bug.  An extension
should be considered only a temporary work-around when there is a report
of a software deficiency.




...the key to what you say here is "functionality" - if it's a new 
feature, or a custom implementation, then yeah.  An add-on solution is fine.


But if it's *broken*, it's *broken* and if you can code an add-on to fix 
something that's actually broken, one would think you just as well fix 
that part of the baseline code - even if it took a couple release 
cycles.  Otherwise the "workaround" becomes just an excuse for inaction.



It depends on the "software deficiency." If only one in a thousand
users, say, considers it a "deficiency," it makes more sense to provide
this extra functionality as an extension, in order to keep from bloating
the basic product.



"Defect" would be a better word to use - if it worked before but doesn't 
now, it's a defect and should/must be fixed.  If it simply doesn't work 
the way someone would *like* it to work, well, one man's "deficiency" is 
another man's "feature" and open for debate.



Generally speaking, all features cost /something/. There's a development
cost, there's a support cost, there's a download size cost, there's a
memory footprint cost, there's a performance cost, there's a UI bloat
cost. Managing those costs is part of the product development. And
sometimes users may have a disagreement with the dev team on whether the
benefits of including a feature offset its costs.



Fixing genuine bugs ("defects" as defined above) should only incur 
support costs - any growth in the code because of that is just 
evolution.  What it sounds like you are saying is that managing cost by 
ignoring defects is a viable and working option...



For instance, during my old BBS days, pre-Internet, I used a message
reader called Blue Wave. It had a very nice built-in tagline management
feature. When I moved to the Internet, I was surprised to find out that
e-mail clients didn't include this feature. It wasn't a deal-breaker,
but I really missed it.



Price of progress...


However, I came to realize that most users didn't care (even in my BBS
days most users never fiddled with that feature). It didn't make sense
to bloat the program and the UI with a seldom-used feature.



Which is again, isn't/wasn't a "defect"...


Eventually, I found an extension that supplied the missing
functionality. I have been using it since. It works for me and doesn't
bloat the program for the 99+% other users who don't care for taglines.



And that's great...but in this instance you're talking about a feature 
of one package you'd have liked to see in another one.  You probably 
should have had zero expectation of that happening in the first place.


But if you'd returned to Blue Wave and seen the feature broken, then 
yeah - you'd be right to complain.


--
 - Rufus
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions As Bug Work-Arounds

[MCBastos]

Interviewed by CNN on 17/03/2012 20:29, David E. Ross told the world:

> And, no, extensions are not sufficient to solve a bug.  An extension
> should be considered only a temporary work-around when there is a report
> of a software deficiency.

It depends on the "software deficiency." If only one in a thousand
users, say, considers it a "deficiency," it makes more sense to provide
this extra functionality as an extension, in order to keep from bloating
the basic product.

Generally speaking, all features cost /something/. There's a development
cost, there's a support cost, there's a download size cost, there's a
memory footprint cost, there's a performance cost, there's a UI bloat
cost. Managing those costs is part of the product development. And
sometimes users may have a disagreement with the dev team on whether the
benefits of including a feature offset its costs.

For instance, during my old BBS days, pre-Internet, I used a message
reader called Blue Wave. It had a very nice built-in tagline management
feature. When I moved to the Internet, I was surprised to find out that
e-mail clients didn't include this feature. It wasn't a deal-breaker,
but I really missed it.

However, I came to realize that most users didn't care (even in my BBS
days most users never fiddled with that feature). It didn't make sense
to bloat the program and the UI with a seldom-used feature.

Eventually, I found an extension that supplied the missing
functionality. I have been using it since. It works for me and doesn't
bloat the program for the 99+% other users who don't care for taglines.

-- 
MCBastos

This message has been protected with the 2ROT13 algorithm. Unauthorized
use will be prosecuted under the DMCA.

-=-=-
... Sent from my Total Lack of Social Skills.
* Added by TagZilla 0.7a1 running on Seamonkey 2.8 *
Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions As Bug Work-Arounds

[David Cox]

On 18/03/2012 9:29 AM, David E. Ross wrote:

On 3/17/12 3:13 PM, Ray_Net wrote:

David E. Ross wrote, On 17/03/2012 20:10:

I have 18 extensions installed for SeaMonkey.  Seven of them are
installed only because various bug reports have not been fixed.  The
extensions and the related bugs are:






And, no, extensions are not sufficient to solve a bug.  An extension
should be considered only a temporary work-around when there is a report
of a software deficiency.


I agree ... but ...

In an ideal world, or with a product that you pay for. However when the 
work is being done by volunteers out of altruistic zeal you get what you 
pay for i.e. pay some one to implement your required fix or do it yourself.


Mind you, a volunteer (individual or council) can still break things 
because they want to implement something else that is incompatible. But 
this happens with commercial products too.


There are no easy solutions, however you may wish for them.

djc
[having read these discussions for years now]




___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions As Bug Work-Arounds

[David E. Ross]

On 3/17/12 3:13 PM, Ray_Net wrote:
> David E. Ross wrote, On 17/03/2012 20:10:
>> I have 18 extensions installed for SeaMonkey.  Seven of them are
>> installed only because various bug reports have not been fixed.  The
>> extensions and the related bugs are:
>>
>> * Find Preferences: Bug 505196 at
>> 
>>
>> * Old Default Image Style: Bug 717226 at
>> 
>>
>> * Password Exporter: Bug 664574 at
>> 
>>
>> * Preserve Download Modification Timestamp: Bug 733954 at
>> 
>>
>> * Remember Passwords: Bug 425145 at
>> 
>>
>> * Show Password On Input: Bug 232050 at
>> 
>>
>> * Show my Password: Bug 502258 at
>> 
>>
>> Additionally, I have had to install or create some "buttons" in the
>> PrefBar extension as work-arounds for other bug reports.  The bugs are:
>> Bug 526150 (WontFix) at
>> 
>> Bug 660646 at
>> Bug 664574 at
>>
>> Some of these work-arounds -- both extensions and PrefBar "buttons" --
>> are not being maintained.  Thus, I am concerned that the lack of
>> activity to implement fixes for the bug reports might reduce the
>> functionality of future versions of SeaMonkey unacceptably.
>>
>> No, not all of these bug reports are SeaMonkey.  Some are Core and
>> Toolkit bugs.
>>
> Did you expect at least one problem solved ? (solved-corrected, not 
> solved-wontfix :-) )

Yes.  Rather than adding new "improvements" (not all of which are indeed
improvements. e.g., bug 376997), some attention should be given to older
bug reports.

And, no, extensions are not sufficient to solve a bug.  An extension
should be considered only a temporary work-around when there is a report
of a software deficiency.

-- 

David E. Ross
.

Anyone who thinks government owns a monopoly on inefficient, obstructive
bureaucracy has obviously never worked for a large corporation.
© 1997 by David E. Ross
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions As Bug Work-Arounds

[Ray_Net]

David E. Ross wrote, On 17/03/2012 20:10:

I have 18 extensions installed for SeaMonkey.  Seven of them are
installed only because various bug reports have not been fixed.  The
extensions and the related bugs are:

* Find Preferences: Bug 505196 at


* Old Default Image Style: Bug 717226 at


* Password Exporter: Bug 664574 at


* Preserve Download Modification Timestamp: Bug 733954 at


* Remember Passwords: Bug 425145 at


* Show Password On Input: Bug 232050 at


* Show my Password: Bug 502258 at


Additionally, I have had to install or create some "buttons" in the
PrefBar extension as work-arounds for other bug reports.  The bugs are:
Bug 526150 (WontFix) at

Bug 660646 at
Bug 664574 at

Some of these work-arounds -- both extensions and PrefBar "buttons" --
are not being maintained.  Thus, I am concerned that the lack of
activity to implement fixes for the bug reports might reduce the
functionality of future versions of SeaMonkey unacceptably.

No, not all of these bug reports are SeaMonkey.  Some are Core and
Toolkit bugs.

Did you expect at least one problem solved ? (solved-corrected, not 
solved-wontfix :-) )

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions, Themes, Ad-Ons - Broken

[Michael Gordon]

Jim Taylor wrote:

Michael Gordon wrote:

I have been a long time user of the Mozilla Suite since Netscape
Communicator.
I have enjoyed customizing my browser to enhance work flow and
productivity.

This last update to 2.8 broke all my ad-ons and has reverted back to a
non-productive graphical web browser.

I have tried downgrading to version 2.7 and they are all still broken.

Is there any help in restoring these ad-ons?

Michael G


For anybody to help they will need to know the OS (looks like maybe
Windows XP from your header), what addons broke and what are the
indications (fail compatibility check, won't load, load and won't run,
etc).

First thing to try is disable all of them using the addon manager,
restarting SeaMonkey and enabling just one of them in case one of them
is causing all the problems.


Lets start with the OS: Windoes XP sr3
The ad-ons are already disabled, they were after installing SM 2.8
There seems no way to enable an ad-on even after editing the install.rdf 
file to be compatible with SM 2.9


Michael G

--
Armadillo Web Development
www.armadilloweb.com

Cell: 903.244.3644

Opening your Door to Opportunity
and inviting the world to walk through.

Character is doing the right thing...
Even when no one is watching...

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions, Themes, Ad-Ons - Broken

[Jim Taylor]

Michael Gordon wrote:

I have been a long time user of the Mozilla Suite since Netscape
Communicator.
I have enjoyed customizing my browser to enhance work flow and
productivity.

This last update to 2.8 broke all my ad-ons and has reverted back to a
non-productive graphical web browser.

I have tried downgrading to version 2.7 and they are all still broken.

Is there any help in restoring these ad-ons?

Michael G


For anybody to help they will need to know the OS (looks like maybe 
Windows XP from your header), what addons broke and what are the 
indications (fail compatibility check, won't load, load and won't run, 
etc).


First thing to try is disable all of them using the addon manager, 
restarting SeaMonkey and enabling just one of them in case one of them 
is causing all the problems.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: extensions, and Components

[JeannineYoung]

freelance writer


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: extensions, and Components

[AlfordOLLIE]

freelance writer


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions for SM2

[Bill Davidsen]

JAS wrote:

When we we be able to install some old favorites to SM2? Right now there
are very few extension available and Themes also. When the final release
of SM2 comes out will all Firefox extgension work for SM2?

Definitely need more themes, although the one I prefer is there, at this time of 
the year the 'Halloween' theme should be available. ;-)


And what works with the RC2/build3 doesn't always work with the daily truck 
(2.1pre) builds either. It seems as though there could be some effort in the 
area of "don't re-invent the wheel with every minor release." Obviously that's a 
discussion for the post-2.0 time frame, read my comment as a suggestion rather 
than complaint.


--
Bill Davidsen 
  "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extensions for SM2

[Martin Freitag]

JAS schrieb:
> When we we be able to install some old favorites to SM2? Right now there
> are very few extension available and Themes also. When the final release
> of SM2 comes out will all Firefox extgension work for SM2?

No, but more than used to work in SM1.x [*]
Also there'S hope that some extension developers will adjust their
extension to work with SM after final release.
regards

Martin

[*] many actually do work if you just override their compatibility.
-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - http://www.gerstbach.at/2004/ascii
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey