On 30/06/2016 4:13 AM, Mark B wrote:
J. Weaver Jr. wrote:
Mark B wrote:
Chase Bank recently updated their websites, and now they won't allow
access using SeaMonkey. They say "You need to upgrade your browser to
access your accounts and statements. Download a new version of your
favorite browser here:
Internet Explorer > (download the latest version.)
Firefox > (download the latest version)
Chrome > (download the lastest version)
Safari >"
I have been using SM for years to access Chase. Not about to use
another browser just to do it their way.
Call Chase Online services (877) 260-2178 and file a complaint. The
first person you talk to can't do anything, so ask to escalate the
complaint. I told them it was their problem, and gave them the user
agent string: (Help/About SM) User agent: Mozilla/5.0 (Windows NT 6.1;
WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40.
If enough people complain, they might do something about it other than
say "We don't support SM." To which the reply should be "I don't
support you."
Solved that problem here by adding this preference to "about:config":
general.useragent.override.chase.com
(type "string") with the following value:
Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0
Yes, it'll have to be updated manually as SM advances, but WORKS4ME. -JW
Thanks for that. It does work, but a PITA to remember every time SM
updates.
Once upon a time, a user could create a plain text file called user.js
and stick personalised prefs in it and those personal prefs would get
incorporated into prefs.js (i.e. about:config) each time SM was re-started.
Does this not apply now??
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
SeaMonkey/2.40 Build identifier: 20160120202951
or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101
SeaMonkey/2.38 Build identifier: 20150903203501
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
