On 20/04/2017 6:45 PM, Paul B. Gallagher wrote:
Ray_Net wrote:
Yes this their fault - a great number of webmasters are doing the
same fault. It is faster and easier to change the default UA string
to FireFox than convincing ALL webmasters to change their coding. But
most of the time, they don't want to change their coding and more ...
they don't know what "Gecko" is, because they sniff for a Browser,
"Gecko" IS NOT a browser. Additionally, if the default UA is
FireFox, we don't need anymore extra plugins or fiddling.
Depends how they do their sniffing. Some sites reject "Firefox/49.0
SeaMonkey/2.46" while accepting "Firefox/49.0" -- presumably because the
first contains something /besides/ "Firefox." But the whole idea of a
coder tripling his effort by writing multiple custom-tailored versions
of his code and sniffing for the user's browser seems so stupid to me....
Yeap!! Long time ago, I came across the saying "When you do something,
do it once, do it well, and move on!"
Sort of been my motto!
If web sites were correctly coded, or sniffed correctly, these problems
would not be a bother.
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101
SeaMonkey/2.46 Build identifier: 20161213183751
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
