On 8/30/2016 at 10:42 AM, David E. Ross's prodigious digits fired off:
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.
When SM loads it reads the user.js file and writes the data into the
prefs.js file and sorts the preferences there.
Also, be aware that deleting the user.js or any entries in it does NOT
remove them from prefs.js.
Further, alterations to either .js file needs to be done with SM closed.
--
Ed Mullen
http://edmullen.net/
"That's a hell of an ambition, to be mellow. It's like wanting to be
senile." - Randy Newman
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
