David E. Ross wrote:
On 1/23/12 3:59 AM, Daniel wrote:
Jens Hatlak wrote:
David E. Ross wrote:
<snip>
By the way, selecting the link
<https://addons.mozilla.org/en-US/seamonkey/addon/betterprivacy/>
redirects to
<https://addons.mozilla.org/en-US/firefox/addon/betterprivacy/>.
This is because AMO seems to only check the latest add-on version, which
is no longer declared compatible with SM (author's fault).
HTH
Jens
Jens, is this possibly caused by the fact that the SM Build ID mentions
FF before SM, e.g...
Build identifier: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0.1)
Gecko/20111221 Firefox/9.0.1 SeaMonkey/2.6.1
so goes looking for FF extensions??
Not in my case. I have disabled "Advertise Firefox compatibility". My
UA string is:
Mozilla/5.0 (Windows NT 5.1; rv:9.0.1) Gecko/20111221 SeaMonkey/2.6.1
There is no "Firefox".
so, obviously, David, it would have no reason to go looking for FF add
ons, however my, stock-standard, Build ID *does*Z mention FF!!
--
Daniel
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
