09:50:46 <Maniel> There is a discussion in alt.comp.software.seamonkey about the *default* User Agent string for SeaMonkey with some suggesting that the stock standard SeaMonkey UA includes a reference to FireFox
09:50:48 <Maniel> Is this the case ..... or does the Stock, Standard UA for SeaMonkey *JUST* include the SeaMonkey 2.53.18.x Version at this time??
14:32:29 <MattATobin> Maniel, SeaMonkey seems to have advertize firefox compat set to be on by default. This is needed because UA sniffing didn't go away it just became far more strict and tied to ESR numbers for those that check for Firefox
14:32:29 <MattATobin> Pale Moon and other UXP Browsers also do the same thing..
14:33:26 <MattATobin> the native UA for SeaMonkey would do two things.. be considered a generic perhaps mobile browser or crawler or be considered current firefox by the gecko slice alone
14:40:07 <njsg> Maniel, (if you read the log), SeaMonkey allows three different UA string behaviours, besides the ability to completely customize it (used by stuff like User-Agent Switcher, for example), and also domain/site-specific overrides
14:40:51 <njsg> it can be as exposed in the UI: either firefox, or seamonkey or firefox+seamonkey
14:40:57 <MattATobin> speaking of.. does seamonkey have rights to retain the usage of the gecko trademark?
14:41:41 <njsg> you *will* encounter sites that break with each of these choices
14:44:27 <MattATobin> the best overall combo would tho be the default.. as saying based on a firefox esr and hoping the patchqueue covers it
14:45:20 <MattATobin> also seems a lot of sites don't always remove fallbacks but merely bump the min version to be dicks
14:45:28 <MattATobin> Google is one of those
14:45:58 <njsg> combining Firefox with SeaMonkey does provide (1) the accurate identification of the browser and (2) the mozilla-like approach to web compatibility from the 90s
14:46:20 <njsg> by mozilla-like I mean how other browsers added "mozilla" to their UAs
14:46:52 <MattATobin> mozilla/6.0
14:46:56 <njsg> one way for this to fail is when sites do check for the Firefox version to determine what is supported
14:47:02 <MattATobin> i fear it will never happen
14:47:37 <MattATobin> why don't people use feature detection to maintain backwards compatibility with browsers
14:47:49 <MattATobin> because supporting just chrome is easier and cheaper
14:47:51 <MattATobin> right
20:40:43 <nsITobin> njsg: Like Gecko;
20:40:53 <nsITobin> nasty never should have been tollerated