Desiree wrote:
I'll complain to, but what a bother
I just got off the phone with Chase websupport. I filed a formal
complaint but it was like pulling teeth to get the rep to do it.
I get the browser upgrade page on SeaMonkey 2.40 and Pale Moon 25.8.1
(x64). On Fx 45.2 ESR, I have a cookie problem that doesn't get solved
even when Chase puts cookies on Fx.
I was told that FIREFOX 24 is the requirement and that has NOT been
changed. I sharply questioned that as Pale Moon is based off Fx 24 and
it worked fine at Chase until now and SeaMonkey 2.40 is based on Fx 43
and it doesn't work now at Chase. She said that she has been taking a
lot of calls from Fx users who even with CURRENT Fx version cannot
access Chase site. She said that those users have no problems accessing
Chase site using Chrome and, thus, that means the problem is a Mozilla
problem not a Chase problem. Chase is blameless and if if I didn't want
to use Chrome then well, I am not required by Chase to access their
website...ever! So, I should just forget accessing it at all. Sigh.
I feel your pain, but as noted in another thread, Chase doesn't care.
For browser handling, they've chosen to be ignorant, and all they're
focusing is on the brand name that users see. Seamonkey isn't Firefox,
and there's nothing you (or any of the rest of us) that's going to make
them change their minds. You and I know that sniffing for "Gecko" is the
solution, but in the eyes of Chase's management, that's too geeky for
them to address. And unfortunately, they've gone so far as to demand
Firefox by name, where the Seamonkey approach of "advertise Firefox
compatibility" gets ignored.
At this point you have three options:
1) Use PrefBar or UserAgentSwitcher to show a full Firefox UA string. In
the past, I've done that with Chase, and not had problems, although it's
been a couple of years since I've needed to interact with Chase. I
prefer PrefBar, and I have it set where I can select the spoofing I
need, when I need it. (For what it's worth, I also sometimes use
spoofing if I'm downloading Mac software for my downloads collection --
some sites that have both Windows and Mac versions of tools will resort
to sniffing and automatically download the version for the platform they
detect. Thus, if I'm wanting to get a Mac version for my downloads
collection, I have to change the UA, so that it shows that I'm running
from a Mac, rather than Windows).
Since I haven't tried Chase recently, I can't guarantee that spoofing
will work, but it's worth a try.
From my own PrefBar settings, I currently have:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
It's a little old, but if spoofing will work at Chase this one should be
adequate.
2) Swallow your pride, and use a prescribed browser for your
interactions with Chase.
On my Seamonkey installation, I have it tweaked radically enough between
use of aggressive cookie handling, AdBlock Plus and NoScript, that there
are some sites that I just can't get to. Sometimes, it's easier to
simply concede that my setting aren't working, and launch a different
browser for that, rather than trying to fight through a bunch of
whitelisting.
3) Change banks. Chase is one of those mega-corporations that if you
leave (even if you tell them you're leaving, and why), they really don't
care. You don't generate enough revenue for them that you're worth the
bother. They may not tell you directly, but if you leave, their attitude
is going to be much closer to "don't let the door hit you on the way
out", rather than falling at your feet, begging you to stay.
We live in a world where "what's hot", "what's trending, etc." governs a
lot of what happens. For those of us that choose to use Seamonkey, we've
chosen to swim against the current, by doing something different. And
the corporate world is mostly unwilling to expend effort and resources
to facilitate that.
Smith
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
