Edmund wrote:
Dustbin wrote:
It should not be necessary to spoof firefox.
If people wrote their code to work to TCP/IP standard protocols SM would
work.
Do you mean putting FireFox in the UA string? If so, that has (AFAIU)
nothing to do with the TCP/IP standard protocols, but the way the
website detects browsers and adapts the website to the user
depending on the UA.
Since (AFAIK) most sites cater to IE, Chrome and Firefox, they care
only about those browsers. Even though SeaMonkey also uses the same
engine as FireFox, our users don't get the same treatment as
FireFox users. If the websites detect the engine instead of the
browser string, it would make it simple and we can just use
SeaMonkey in the UA.
If I've erred.. any corrections appreciated.
It is not that you have erred it is that they should not be abusing the
system's facilities to engineer code for a limited number of browsers.
The code should work equally on all browsers. That is the point of
standards. Writing code with a preference for one or two browsers is wrong.
It is notable that Netscape/Mozilla/SeaMonkey has been around since the
dawn of HTTP and, therefore, is one of the earliest browsers; yet coders
are favouring far more recent browsers such as FireFox and Chrome.
As an erstwhile engineer I favour standards. The usual problem is having
too many of them; but in this case that is not true; there is one
standard for internet transfers (TCP/IP) and one for coding HTTP pages
(W3C). There are issues such as screen width and fixing the relation of
parts of the output to each other. Some of these can be got round. Other
leaves parts of the display off the screen. I have had 1600 pixel width
for many years but others may not. I generally set my pages to 1200
pixel width - which could cause some people a problem.
There are other issues as well, of course, but I still favour observing
standards rather than causing more problems by complicating matters. For
example I used to get a message bar across the top of the screen from
tripadvisor saying that they do not support my browser - it's not there
with SM2.6 so perhaps the FireFox spoofing is fooling tripadvisor into
shutting up and putting up ;-).
D.
Edmund
Edmund
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
