Jens Hatlak wrote:
Daniel wrote:
Jens Hatlak wrote:
David E. Ross wrote:
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).
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??
No. If you go to a /seamonkey/addon/ URL and the latest version of that
add-on is available for SM, then it sticks. The order of occurrences in
the UA has no effect on that. However, once you're on the FF version of
the page, the version check there is wrong (it takes SM's version, puts
"Firefox" in front of it and then displays that to you. Reported
multiple times already.).
HTH
Jens
I just clicked on the ..../seamonkey/addon/betterprivacy/ link above and
got re-directed to the ....../firefox/addon/betterprivacy page again!!
Displays BetterPrivacy 1.68 and asks if I want to add it to Firefox and
mentions that it may be incorporated with FF 2.6.1!!
Note that I was definitely re-directed from the SM page to the FF page.
--
Daniel
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
