Frank-Rainer Grahl wrote:
The option to add Lightning to the UA was recently removed in
Thunderbird and we did it too starting with 2.53.2. Beta 1 is now in
tmp/release and should show up soon.
https://bugzilla.mozilla.org/show_bug.cgi?id=1625750
That one does seem to have caused a number of problems lately, and
doesn't seem particularly useful.
We have some discussions about UA compatibility in Bug 1242294.
https://bugzilla.mozilla.org/show_bug.cgi?id=1242294
A new option will allow for a Firefox only string to please some sites.
Advertizing Firefox and SeaMonkey will be the default.
We are still not sure if the third option dropping Firefox from the UA
is useful. Imho too many sites break without showing Firefox.
For what it's worth, I have "Advertise Firefox compatibility" off, so my
default UA is SeaMonkey-only, and don't have problems with many sites.
I'm not a heavy user of social media or streaming sites though, which
seems to be where a lot of the problems reported recently are. The
banks I use are fine with the SeaMonkey-only UA, but from posts here it
seems American banks are more fussy about it than UK banks are.
The few site-specific overrides I do use all include both Firefox and
SeaMonkey (i.e. they're what I'd get from having "Advertise Firefox
compatibility" on):
- bbc.co.uk (I think it was needed for iPlayer to work properly; one of
the few streaming sites I do use regularly)
- bing.com (probably for their maps; I don't often use Bing anyway)
- mail.google.com (most of Google seems better without Firefox in the
UA, but GMail was better with it; I no longer use it anyway)
- a couple of domains related to my employment which are accessible
externally
- a couple of Scouting-related domains
Personally I think Firefox plus SeaMonkey show be the default and
"Strict Firefox" the only other choice. For sites disliking both a
domain override via about:config or a ua switcher would probably be best.
No final decision yet.
Another thought for the mix - Would it make sense to configure separate
UAs for the browser and for mail/news? Particularly if Firefox-only is
one of the standard options, which doesn't really make sense in mail
headers. The options to advertise Firefox/Lightning are currently both
under "HTTP Networking" in the preferences, but they affect mail/news as
well - i.e. they affect SMTP and NNTP, not just HTTP. It might make
sense to decouple them, so that these options really do only affect
HTTP, while mail/news always uses the SeaMonkey-only UA? (or perhaps
optionally claims to be Thunderbird, although there doesn't seem to be
so much need to mess with the mail/news UA). I don't know how much work
would be involved in decoupling the browser and mail/news UAs, and
appreciate the team is already stretched - just a thought while you're
talking about changes to UA handling anyway.
Google sites will probably all break soon until we implement Custom
Elements and Shadow Dom. Planned but not around the corner.
Google don't seem to need an excuse to break ;o)
--
Mark.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
