Daniel wrote on 03/09/2016 12:08:
On 3/09/2016 4:56 AM, Arnie Goetchius wrote:
David E. Ross wrote:
On 8/30/2016 7:01 AM, Ed Mullen wrote:
On 8/30/2016 at 9:35 AM, JAS's prodigious digits fired off:
Ed Mullen wrote:
On 6/29/2016 at 2:13 PM, Mark B's prodigious digits fired off:
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.
If you put it in a user.js file it will carry over to an update.
It does not work for me using Windows XP and Seamonkey 2.40, any
ideas??
JAS
The full syntax is:
user_pref("general.useragent.override.chase.com", "Mozilla/5.0
(Windows
NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0");
NOTE WELL: The semi-colon (;) at the end is mandatory. Also, I found
that it helps if entries in user.js are alphabetized by the names of
the
preference variables; if this is not a SeaMonkey issue, it is at
least a
human issue.
As of today, I can now log into the Chase website with the default User
Agent for Seamonkey. This is what my UA shows:
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40
Well that's not the default User Agent string, as the default does not
mention Firefox! See mine below......
Anyway; It's a good news ... Chase accept SeaMonkey with Advertise
Firefox compatibility checked.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
