David E. Ross wrote:
On 12/28/10 9:15 PM, Ant wrote:
On 12/27/2010 10:54 PM PT, NoOp typed:
... version for the test& thought that I had clicked the 2.0.11. The reason
why the 2.1b version works is that the UA string includes "Firefox" in
the UA string (as Barry also pointed out).
Wait, v2.1 beta is using Firefox in its user agent? Um, why? That's not
a true user agent for SeaMonkey. :(
I agree. However, it seems this is a "done deal". It was discussed
thoroughly both here and in the bug report. See
<https://bugzilla.mozilla.org/show_bug.cgi?id=572650>.
Apparently, Robert Kaiser was not happy about this. See
<https://bugzilla.mozilla.org/show_bug.cgi?id=591617>. The result of
all this has been several bug reports against Mozilla Web sites --
especially<https://addons.mozilla.org/> -- that sniff the UA string.
It appears that all aspects of this change were not really evaluated.
Bug #572650 may be breaking more than it fixes. Note that, this bug
report really does not describe a discrepancy in software; yet the
developers refuse to classify it as an RFE (request for enhancement).
When you first install the SM-2.1 (currently b2pre), the Firefox UA
probably is turned-on by-default, but it is easily toggled-off via the
menu:-
Edit > Preferences > Advanced > HTTP-networking > User Agent String >
and uncheck the "Advertise Firefox compatibility" box. No about:config
scenario required.
I can't remember what the initial state is as I usually have it off, but
it probably is turned-on to allow new users and people like me who
forget to turn it back on when encountering problem sites, to surf
without having to deal with that extra angst.
Oh, through dozens/hundreds of nightly upgrades which completely-clear
the entire application-folder, but not the profile, the
Firefox-UA-switch stays turned-off, in accordance with my preferences.
HTH. Barry.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
