David H. Durgee wrote:
As of 23 September the Chase website no longer works properly with
2.49.5 here. I find it is impossible to download transactions from a
credit card account, the button to do so no longer works.
I complained to Chase about it, but was told simply to use a newer
browser with their website.
In my experience, Chase has always been one of the most aggressive in
demanding Firefox, to the exclusion of everything else.
From their perspective, what they allow or don't is mostly based on
them having a known UI navigation path, for support purposes. If a
customer is having browser-related problems, they want to be able to say
"Click this, go here, select that", and no more. They don't want to be
bothered with "functional equivalent". Thus, if the configs for Firefox
are reached via going to the hamburger menu and selecting Options, and
Seamonkey configs are reached through Tools -> Options, that's already
more difference than they want to bother with, even without accounting
for the UI difference between Firefox and Seamonkey configs. And
they're unwilling to waste time trying to find a specific setting in an
unfamiliar display. The difference makes Seamonkey a non-starter, even
without accounting for differences between historic Mozilla
architecture, and more recent revisions.
I've found this effect across a lot of financial institutions, although
as noted, Chase has always been most aggressive in rejecting
non-Firefox, rather than allowing "this is what we support -- if you
want to use something else, you're welcome to try, but if you have
problems, we won't help". For my own bank, I'm getting complaints
about a dated browser on 2.49.5 (mostly for security issues), although
they give me the option of ignoring, and if I spoof FF 60, the warnings
go away.
Something that I've never really explored is the handling of other
derivative browsers, including PaleMoon and WaterFox in the Mozilla
family, Chromium-based browsers, such as Iron, Epic, Opera (or even
Chromium itself), or multi-engine browsers such as Lunascape. I don't
know if sites like this that are restrictive in what they will allow
have problems with browsers that are derivatives (and identify
themselves as derivatives).
This appears to definitely use features only available in a later
Firefox release, as spoofing a current Firefox does not solve the
problem. In fact using the default UA causes the website fits where it
loops while loading without end, so I have to spoof Firefox 52 ESR to
get it to load at all.
It's entirely possible that Chase actually does have something that
requires something in Firefox 60. It's also possible that regard
anything older than FF 60 to be sufficiently old that they don't want
people using browsers with known security holes.
This is the second website that is unusable with 2.49.5 that I need
access to. I hope that its successor will no be long in coming so that
I can get back to using a single browser for those website I need to use.
For me, I've more or less gotten used to using more than one browser. I
do enough tweaking of my primary browser with things like NoScript and
UBlock Origin (including making sure I have the latest versions of those
that will run on Seamonkey) that there's a growing number of sites that
are so heavy on tracking and scripting that it's difficult to get them
to work in my regular profile. Thus, one reason that I keep "bare
metal" profiles (both Firefox and Seamonkey), with nearly zero
non-default settings. If I'm having problems getting a site to behave in
my regular profile, it's often fastest/easiest to simply use the Bare
Metal profile in Firefox, especially with commerce sites.
Smith
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
