Samuel S wrote:
Hello all -
Having issues with verizon.com login stalling and not connecting and
Chase indicating that the browser is no longer supported...
They both work like a charm in chrome...
TIA for your input and assistance - bo1953
I haven't seen verizon.com, but chase.com has a long history of being
exceptionally fussy about demanding *only* current versions of Firefox,
Chrome or Safari (or I guess, now, Chrome-based Edge). Check the
archives of this newsgroup, there's several threads that explicitly
mention Chase.
I find this to be somewhat common at the web sites for various financial
institutions. Although objections may be framed as making sure you have
the latest features of a browser, it's pretty rare (and I'm not sure
I've ever encountered myself) a site that requires features that weren't
included with Firefox 52.x.
The real issue tends to be a matter of technical support. Using Chase as
example, if you're having problems, and you tell them you're using
Firefox 78.3, they'll tell you "click here, here, here and then select
this option". If you tell them that you're running Seamonkey, you'll
get the equivalent of a dialtone. It's not that the site requires
something that Seamonkey won't do, but that the UI for getting to
specific settings is different, and they are unwilling to spend the time
guessing about where to locate the same setting. It would not surprise
me if Chase has a corporate guideline to try to limit all customer
support sessions to less than something like 4 minutes (or less, if
possible). Allowing users to use something does serious damage to those
metrics.
As noted elsewhere in this thread, the best work-around is through
spoofing, and setting an entry in about:config
general.useragent.override.chase.com
set to
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101
Firefox/81.0
At this stage, showing 68.0 is sufficient, although I would probably
recommend 78.0 (which is shown by all current versions of Firefox ESR
78.x) and you don't have to change it as often.
I will note that I do the same thing with a couple of my own financial
institutions (even if they're less extreme than Chase about demanding
preferred browsers). Also, I do this for google.com, as a way of fixing
a display quirk that shows up in Google's search bar. If I show a stock
Firefox UA string to Google, then their display works correctly. If I
show a UA string that includes both Seamonkey and Firefox, then the
problem persists.
For what it's worth, this issue applies to all Firefox-derived browsers,
not just Seamonkey. I've seen it with PaleMoon, and I assume that it's
also an issue in Waterfox, although I haven't seen that.
It's not that they're persecuting Seamonkey specifically, just that they
want "Firefox or nothing". With spoofing, you can show them what they
want to see (and where you assume that you're not going to need their
support help), and continue using the browser you want to.
Smith
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
