Rufus wrote:
If I have to use or even know anything about about:config to get
something in SM to work, that's a "hack". That's the sort of thing I was
referring to. Not documentation.
Sure. But that's as good as we can get. We cannot force the add-on
authors to do anything. We cannot change the add-on install back-end
because it's part of the platform (well, some knowledgeable developer
could fork the code, but no-one has the time to maintain that!).
So we only have two alternatives:
a) Say that whatever is incompatible is just that and be done with it.
Not our fault, not our problem. Deal with it. If you want to get
something to work, find out yourself.
b) Try as good as we can do document the state of affairs and what you
can do in the different cases. Ask add-on authors to update the
compatibility of their add-ons. Tell everyone to use the Add-on
Compatibility Reporter in order to help the process.
But I'll add that I've read enough complaints here that I'm not even
interested in trying the 2.1 or 2.2 because too many people are saying
that too many things I depend on are broken. I'll wait for 2.3+, and
only then after I upgrade to Lion.
Fair enough. But be told that 2.3 and probably also 2.4 will not contain
too many changes beside *some* bug fixes. With the rapid release train,
releases come more frequent, but that also gives us much less time to
fix things (or work on features, which takes even longer).
HTH
Jens
--
Jens Hatlak <http://jens.hatlak.de/>
SeaMonkey Trunk Tracker <http://smtt.blogspot.com/>
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
