I'm not using Firefox compatibility mode because I don't want to imitate Fx and make thus false statistics. Unfortunately, some sites are requesting specific browsers (instead of functions). For such sites I'm using "UserAgent Site Specific Overrides" function.
I've been informed about one bank in Poland with strange behavior when SM is using override function when trying to login:
1) if user have SeaMonkey UA then is informed about "wrong browser"
2) if override function is set up (via "about:config"):
- Code: Select all
user_pref("general.useragent.override.getinbank.pl", "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46");
... then above site is reloading all the time and without pause, immediately.
3) only compatibility mode works correct.
I'm not their client/customer so I can't complain about "wrong browser".
But I was curious how it is possible for website to not detect UA... and after some testing (new profiles, different systems, portable versions) it looks like a bug in SeaMonkey 2.46 (both Windows and Linus version; Linux Mint 18 Sarah) because version 2.40 works correct. I've set up in SM 2.40 the same UA like for 2.46 (see: above code) and bank's website loaded correctly.
I don't know how it is possible because User Agent override works correct for UA recognition site like:
I hope it's just a bug that can be fixed not some "Fx code castration's fallout"...