Following up several responses in a single post...
Zeb Carter wrote:
David H. Durgee wrote:
Ken Rudolph wrote:
David H. Durgee wrot
e:
Ken Rudolph wrote:
Thank you SeaMonkey team! One seriously annoying bug fixed. Still,
after several months, the Chase (and also the BofA) sites still have
For this, I think the problem is not with Seamonkey, but brain-dead
developers who know only about Firefox, not that Firefox is merely the
most prominent browser built on Gecko (http://geckoisgecko.org). Since
the time that Seamonkey developers went with spoofing Firefox in ID
string (and including the Seamonkey name), I've found that the number of
conflicts has been minimal.
There's a couple of extensions that allow for spoofing -- Browser Agent
Switcher, and PrefsBar. It's been a long time since I've needed to
spoof Firefox, although I occasionally will spoof my platform to allow
for downloads of Mac versions of stuff for my software collection. Some
sites look for Browser Agent strings for contextual delivery of
downloads (by platform). And even if I don't often need to spoof my
browser identity, I've found that there's several other settings in
PrefsBar that I find really useful.
In any case, it's been long enough since I've had the misfortune of
having to connect to Chase, that I forgot that their developers are of
the brain-dead variety, in how they identify browsers, and their
assumptions of users' work flows. I know that they're trying to do
security, but I find their aggressive offering of "remember password"
show that they don't really get it, in assuming that user presence at a
keyboard is sufficient to authenticate the user.
I wish there were some easy way to alter the user-agent line to
preference the Firefox version, since asking the banks to accept
SeaMonkey as a valid browser over and over gets nowhere.
That is why I copied the FireFox user agent string and added it to
PrefBar as an additional user agent. I now tend to leave this set as my
user agent string to avoid this very idiotic message there and
elsewhere.
See above. Yes, you can change your user agent in prefs.js, but that
hard-codes things, and you have to update every time that Mozilla does
another update cycle.
One minor glitch that I've discovered with spoofing in Seamonkey is that
it affects your email, as well. When you send mail, User-Agent: is also
a header line. I use the dispMUA extension that shows a message's
User-Agent: header (useful for providing tech support, to know which
client a user is using), as an icon in the message header display. A
few days ago, I was sorting out my Sent Mail folder, and noticed that
several messages that I had sent were showing a Firefox logo. On
further investigation, I discovered that those messages had been sent,
when I had Seamonkey spoofing that I was running Firefox on a Mac.
Could you specify exactly how you added the FireFox user-agent string to
the PrefBar. For somebody who is tech stupid, that is. There used to
be a way in the Tools menu to manage the user-agent. That hasn't been
around for a while.
For this one, I happen to have Firefox installed on my machine, because
I provide tech support for Firefox users. Going to Help -> About shows
what Firefox is showing.
To add to this, go to http://www.useragentstring.com/
You can cut and paste any of the user agent strings to spoof other browsers.
This is good stuff, although a quick look indicates that they're a
couple of release cycles behind, at least for Seamonkey. Firefox looks
current. However, if you look at several of the most current settings,
it's easy enough to interpolate up to most current versions. In my
case, since I spoof both platform and browser, it's definitely useful
for getting the detail of what I want.
Smith
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
