Re: Chase Bank doesn't like SeaMonkey

Sorry folks, I gave the wrong URL and file name. The correct ones are: https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/ and seamonkey-2.46.en-US.win64.installer.exe

Re: Chase Bank doesn't like SeaMonkey

The instructions provided by J. Weaver Jr. did the trick for me and are worth repeating: * In a browser page address bar, type "about:config" (without the quotes). * Anywhere in the body of the page, right click, select "New" and "String". * At the "Enter the

Re: Chase Bank doesn't like SeaMonkey

On 10/29/2016 7:39 PM, JAS wrote: > J. Weaver Jr. wrote: > >> >> In a browser page address bar, type "about:config" (without the quotes). >> >> Anywhere in the body of the page, right click, select "New" and "String". >> >> At the "Enter the preference name" prompt, type >>

Re: Chase Bank doesn't like SeaMonkey

JAS wrote: J. Weaver Jr. wrote: In a browser page address bar, type "about:config" (without the quotes). Anywhere in the body of the page, right click, select "New" and "String". At the "Enter the preference name" prompt, type "general.useragent.override.chase.com" (without the quotes). At

Re: Chase Bank doesn't like SeaMonkey

J. Weaver Jr. wrote: In a browser page address bar, type "about:config" (without the quotes). Anywhere in the body of the page, right click, select "New" and "String". At the "Enter the preference name" prompt, type "general.useragent.override.chase.com" (without the quotes). At the next

Re: Chase Bank doesn't like SeaMonkey

NFN Smith composed on 2016-10-29 10:17 (UTC-0700): Felix Miata wrote: ...automate... ...user.js... only -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Re: Chase Bank doesn't like SeaMonkey

On 10/29/2016 8:58 AM, Felix Miata wrote: > NFN Smith composed on 2016-10-29 08:41 (UTC-0700): > >> Thus, your choices for that are either hard-coding into prefs.js (which >> you'll need to remove when you upgrade Seamonkey), or using one of the >> extensions noted here. > >> However, when you

Re: Chase Bank doesn't like SeaMonkey

Felix Miata wrote: One should only ever manipulate prefs.js manually in the most extreme of circumstances, and only with knowledge of the consequences. The right way to automate inclusion of a prefs override is via user.js, a purely optional profile file that SM will only read from, never write

Re: Chase Bank doesn't like SeaMonkey

NFN Smith composed on 2016-10-29 08:41 (UTC-0700): Thus, your choices for that are either hard-coding into prefs.js (which you'll need to remove when you upgrade Seamonkey), or using one of the extensions noted here. However, when you resort to spoofing you do have do a little maintenance

Re: Chase Bank doesn't like SeaMonkey

Marisa Ciceran wrote: I have been a faithful user of Seamonkey and its predecessors since the mid-1990s. Have there been no updates to Seamonkey since the release of version 2.40 in March 2016? That's correct. It is for months that I have been unable to log into my Chase bank accounts

Re: Chase Bank doesn't like SeaMonkey

On 10/29/2016 11:20 AM, David E. Ross wrote: On 10/29/2016 5:11 AM, Marisa Ciceran wrote: I have been a faithful user of Seamonkey and its predecessors since the mid-1990s. Have there been no updates to Seamonkey since the release of version 2.40 in March 2016? It is for months that I have

Re: Chase Bank doesn't like SeaMonkey

On 10/29/2016 5:11 AM, Marisa Ciceran wrote: > I have been a faithful user of Seamonkey and its predecessors since the > mid-1990s. Have there been no updates to Seamonkey since the release of > version 2.40 in March 2016? > > It is for months that I have been unable to log into my Chase bank

Re: Chase Bank doesn't like SeaMonkey

Marisa Ciceran wrote: I have been a faithful user of Seamonkey and its predecessors since the mid-1990s. Have there been no updates to Seamonkey since the release of version 2.40 in March 2016? It is for months that I have been unable to log into my Chase bank accounts because chase.com claims

Re: Chase Bank doesn't like SeaMonkey

I have been a faithful user of Seamonkey and its predecessors since the mid-1990s. Have there been no updates to Seamonkey since the release of version 2.40 in March 2016? It is for months that I have been unable to log into my Chase bank accounts because chase.com claims that Seamonkey is

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 10/25/2016 8:12 AM, Rick Merrill wrote: Some of the TOOLS for webpages only support certain browsers, but not standards. There should be an underwriters' lab for web pages ;-) Actually there is. "The World Wide Web Consortium (W3C) is an international community where Member

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/7/2016 10:41 AM, Ray_Net wrote: Ed Mullen wrote on 07/09/2016 16:15: On 9/7/2016 at 7:31 AM, Daniel's prodigious digits fired off: On 7/09/2016 5:15 AM, Ray_Net wrote: David E. Ross wrote on 05/09/2016 22:38: On 9/5/2016 12:17 PM, Ray_Net wrote: Jerry wrote on 04/09/2016 15:12: I've

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with Modified User.js

WaltS48 wrote: > On 09/13/2016 09:03 PM, Arnie Goetchius wrote: >> When I open SM using the profile for Default User, I get exactly what >> you get. However, when I open SM using my regular profile, I can access >> the Chase site with no problem. I modified the user.js file as suggested >> by

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 09/13/2016 09:03 PM, Arnie Goetchius wrote: When I open SM using the profile for Default User, I get exactly what you get. However, when I open SM using my regular profile, I can access the Chase site with no problem. I modified the user.js file as suggested by Dennis Ross and that lets me in

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

Lemuel Johnson wrote: > On 9/13/2016 4:25 PM, Arnie Goetchius wrote: >> Lemuel Johnson wrote: >>> On 9/13/2016 9:48 AM, Ed Mullen wrote: On 9/12/2016 at 6:45 PM, Lemuel Johnson's prodigious digits fired off: > On 9/12/2016 12:04 PM, Ed Mullen wrote: >> On 9/12/2016 at 12:24 PM, Lemuel

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/13/2016 4:25 PM, Arnie Goetchius wrote: Lemuel Johnson wrote: On 9/13/2016 9:48 AM, Ed Mullen wrote: On 9/12/2016 at 6:45 PM, Lemuel Johnson's prodigious digits fired off: On 9/12/2016 12:04 PM, Ed Mullen wrote: On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired off: On

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

Lemuel Johnson wrote: > On 9/13/2016 9:48 AM, Ed Mullen wrote: >> On 9/12/2016 at 6:45 PM, Lemuel Johnson's prodigious digits fired off: >>> On 9/12/2016 12:04 PM, Ed Mullen wrote: On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired off: > On 9/11/2016 8:19 PM, Ed Mullen

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/13/2016 9:48 AM, Ed Mullen wrote: On 9/12/2016 at 6:45 PM, Lemuel Johnson's prodigious digits fired off: On 9/12/2016 12:04 PM, Ed Mullen wrote: On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired off: On 9/11/2016 8:19 PM, Ed Mullen wrote: On 9/11/2016 at 4:31 PM, Lemuel

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/12/2016 at 6:45 PM, Lemuel Johnson's prodigious digits fired off: On 9/12/2016 12:04 PM, Ed Mullen wrote: On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired off: On 9/11/2016 8:19 PM, Ed Mullen wrote: On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off:

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/12/2016 6:22 PM, Paul B. Gallagher wrote: > David E. Ross wrote: > >> On 9/12/2016 2:16 PM, Paul B. Gallagher wrote: >>> But if cookies.sqlite is marked "read-only," how can a site set a >>> cookie, even if it's an approved site? I mean, the definition of "set a >>> cookie" includes "modify

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

Lemuel Johnson wrote: > On 9/12/2016 12:31 PM, David E. Ross wrote: >> On 9/12/2016 9:24 AM, Lemuel Johnson wrote: >>> snipped >>> >>> I appreciate the suggestions. But as a SeaMonkey proponent, maybe even >>> evangelist, I have convinced several friends and family members to use >>> SM as their

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

David E. Ross wrote: On 9/12/2016 2:16 PM, Paul B. Gallagher wrote: But if cookies.sqlite is marked "read-only," how can a site set a cookie, even if it's an approved site? I mean, the definition of "set a cookie" includes "modify cookies.sqlite," does it not? Confusinger and confusinger...

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

Lemuel Johnson wrote: > On 9/12/2016 12:31 PM, David E. Ross wrote: >> On 9/12/2016 9:24 AM, Lemuel Johnson wrote: >>> snipped >>> >>> I appreciate the suggestions. But as a SeaMonkey proponent, maybe even >>> evangelist, I have convinced several friends and family members to use >>> SM as their

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/12/2016 2:16 PM, Paul B. Gallagher wrote: > David E. Ross wrote: >> On 9/12/2016 10:37 AM, Paul B. Gallagher wrote: >>> David E. Ross wrote: >>> I had to create a separate SeaMonkey profile for accessing my financial accounts at a bank, two credit unions, and Vanguard mutual

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/12/2016 12:31 PM, David E. Ross wrote: On 9/12/2016 9:24 AM, Lemuel Johnson wrote: snipped I appreciate the suggestions. But as a SeaMonkey proponent, maybe even evangelist, I have convinced several friends and family members to use SM as their browser and email client. They also have

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/12/2016 12:04 PM, Ed Mullen wrote: On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired off: On 9/11/2016 8:19 PM, Ed Mullen wrote: On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off: On 9/10/2016 12:28 PM, Ed Mullen wrote: On 9/10/2016 at 12:50 PM,

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

David E. Ross wrote: On 9/12/2016 10:37 AM, Paul B. Gallagher wrote: David E. Ross wrote: I had to create a separate SeaMonkey profile for accessing my financial accounts at a bank, two credit unions, and Vanguard mutual funds. My settings for this profile might give you some idea of what

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/12/2016 10:37 AM, Paul B. Gallagher wrote: > David E. Ross wrote: > >> I had to create a separate SeaMonkey profile for accessing my >> financial accounts at a bank, two credit unions, and Vanguard mutual >> funds. My settings for this profile might give you some idea of what >> you might

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

David E. Ross wrote: I had to create a separate SeaMonkey profile for accessing my financial accounts at a bank, two credit unions, and Vanguard mutual funds. My settings for this profile might give you some idea of what you might need to do. Where I say "Normally", that reflects the profile

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/12/2016 9:24 AM, Lemuel Johnson wrote: > On 9/11/2016 8:19 PM, Ed Mullen wrote: >> On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off: >>> On 9/10/2016 12:28 PM, Ed Mullen wrote: On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off: > On 9/2/2016

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired off: On 9/11/2016 8:19 PM, Ed Mullen wrote: On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off: On 9/10/2016 12:28 PM, Ed Mullen wrote: On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off:

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/11/2016 8:19 PM, Ed Mullen wrote: On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off: On 9/10/2016 12:28 PM, Ed Mullen wrote: On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off: On 9/2/2016 1:56 PM, Arnie Goetchius wrote: snipped< As of today, I

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 09/11/2016 04:31 PM, Lemuel Johnson wrote: On 9/10/2016 12:28 PM, Ed Mullen wrote: On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off: On 9/2/2016 1:56 PM, Arnie Goetchius wrote: snipped< As of today, I can now log into the Chase website with the default User Agent

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/11/2016 6:19 PM, Ed Mullen wrote: > > Change banks. That is what I suggested more than two weeks ago. -- Donald Trump claims everyone likes him. Does that include his ex-wives? How about the students who discovered that their education at Trump University was worthless? And how about

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 09/11/16 4:50 PM, Lee wrote: On 9/11/16, Lemuel Johnson wrote: On 9/10/2016 12:28 PM, Ed Mullen wrote: On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off: On 9/2/2016 1:56 PM, Arnie Goetchius wrote: snipped< As of today, I can now log into the Chase

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off: On 9/10/2016 12:28 PM, Ed Mullen wrote: On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off: On 9/2/2016 1:56 PM, Arnie Goetchius wrote: snipped< As of today, I can now log into the Chase website with

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/11/16, Lemuel Johnson wrote: > On 9/10/2016 12:28 PM, Ed Mullen wrote: >> On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off: >>> On 9/2/2016 1:56 PM, Arnie Goetchius wrote: snipped< As of today, I can now log into the Chase website with the

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/10/2016 12:28 PM, Ed Mullen wrote: On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off: On 9/2/2016 1:56 PM, Arnie Goetchius wrote: snipped< As of today, I can now log into the Chase website with the default User Agent for Seamonkey. This is what my UA shows:

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off: On 9/2/2016 1:56 PM, Arnie Goetchius wrote: snipped< 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)

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/2/2016 1:56 PM, Arnie Goetchius wrote: snipped< 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 Chase is still not allowing me

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

Ed Mullen wrote on 07/09/2016 16:15: On 9/7/2016 at 7:31 AM, Daniel's prodigious digits fired off: On 7/09/2016 5:15 AM, Ray_Net wrote: David E. Ross wrote on 05/09/2016 22:38: On 9/5/2016 12:17 PM, Ray_Net wrote: Jerry wrote on 04/09/2016 15:12: I've been following this thread with much

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/7/2016 at 7:31 AM, Daniel's prodigious digits fired off: On 7/09/2016 5:15 AM, Ray_Net wrote: David E. Ross wrote on 05/09/2016 22:38: On 9/5/2016 12:17 PM, Ray_Net wrote: Jerry wrote on 04/09/2016 15:12: I've been following this thread with much interest, since I had the same problem

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 7/09/2016 5:15 AM, Ray_Net wrote: David E. Ross wrote on 05/09/2016 22:38: On 9/5/2016 12:17 PM, Ray_Net wrote: Jerry wrote on 04/09/2016 15:12: I've been following this thread with much interest, since I had the same problem with CHASE. I am happy to report that as of today I can now log

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

David E. Ross wrote on 05/09/2016 22:38: On 9/5/2016 12:17 PM, Ray_Net wrote: Jerry wrote on 04/09/2016 15:12: I've been following this thread with much interest, since I had the same problem with CHASE. I am happy to report that as of today I can now log into my Chase account with Seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

David E. Ross wrote: On 9/5/2016 12:17 PM, Ray_Net wrote: Jerry wrote on 04/09/2016 15:12: I've been following this thread with much interest, since I had the same problem with CHASE. I am happy to report that as of today I can now log into my Chase account with Seamonkey 2.45 on Linux. I

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/5/2016 12:17 PM, Ray_Net wrote: > Jerry wrote on 04/09/2016 15:12: >> I've been following this thread with much interest, since I had the >> same problem with CHASE. I am happy to report that as of today I can >> now log into my Chase account with Seamonkey 2.45 on Linux. >> >> I have the

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

Jerry wrote on 04/09/2016 15:12: I've been following this thread with much interest, since I had the same problem with CHASE. I am happy to report that as of today I can now log into my Chase account with Seamonkey 2.45 on Linux. I have the User Agent Switcher addon installed. In that I entered

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

I've been following this thread with much interest, since I had the same problem with CHASE. I am happy to report that as of today I can now log into my Chase account with Seamonkey 2.45 on Linux. I have the User Agent Switcher addon installed. In that I entered a new User Agent I named

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 4/09/2016 12:20 AM, WaltS48 wrote: On 09/03/2016 10:07 AM, Daniel wrote: On 3/09/2016 11:16 PM, WaltS48 wrote: Daniel wrote: On 3/09/2016 4:56 AM, Arnie Goetchius wrote: As of today, I can now log into the Chase website with the default User Agent for Seamonkey. This is what my UA

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 9/3/2016 7:07 AM, Daniel wrote: > On 3/09/2016 11:16 PM, WaltS48 wrote: >> Daniel wrote: >>> On 3/09/2016 4:56 AM, Arnie Goetchius wrote: >> >> >> As of today, I can now log into the Chase website with the default User Agent for Seamonkey. This is what my UA shows:

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 09/03/2016 10:07 AM, Daniel wrote: On 3/09/2016 11:16 PM, WaltS48 wrote: Daniel wrote: On 3/09/2016 4:56 AM, Arnie Goetchius wrote: 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;

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

On 3/09/2016 11:16 PM, WaltS48 wrote: Daniel wrote: On 3/09/2016 4:56 AM, Arnie Goetchius wrote: 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

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

Daniel wrote: > 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.

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

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

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

Daniel wrote: On 3/09/2016 4:56 AM, Arnie Goetchius wrote: 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

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

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

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

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

Re: Chase Bank doesn't like SeaMonkey

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

Re: Chase Bank doesn't like SeaMonkey

On 8/30/16, JAS wrote: > 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

Re: Chase Bank doesn't like SeaMonkey

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

Re: Chase Bank doesn't like SeaMonkey

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

Re: Chase Bank doesn't like SeaMonkey

On 8/30/2016 at 5:24 AM, Daniel's prodigious digits fired off: On 30/08/2016 12:03 AM, 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

Re: Chase Bank doesn't like SeaMonkey

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.

Re: Chase Bank doesn't like SeaMonkey

On 30/08/2016 12:03 AM, 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

Re: Chase Bank doesn't like SeaMonkey

On 8/29/2016 4:50 AM, Daniel wrote: > 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

Re: Chase Bank doesn't like SeaMonkey

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

Re: Chase Bank doesn't like SeaMonkey

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

Re: Chase Bank doesn't like SeaMonkey

On 30/06/2016 02:13, Mark B wrote: > J. Weaver Jr. wrote: >> Mark B wrote: >> 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)

Re: Chase Bank doesn't like SeaMonkey

On 18/07/2016 6:06 AM, Rick Merrill wrote: On 7/17/2016 7:58 AM, Daniel wrote: I just logged into Chase this morning at this URL: https://chaseonline.chase.com/Logon.aspx?fromLoc=ALL=COLLogon Did it give you a survey about the web site? Rick, you may think, from the attributes quoted

Re: Chase Bank doesn't like SeaMonkey

On 7/17/2016 7:58 AM, Daniel wrote: I just logged into Chase this morning at this URL: https://chaseonline.chase.com/Logon.aspx?fromLoc=ALL=COLLogon Did it give you a survey about the web site? ___ support-seamonkey mailing list

Re: Chase Bank doesn't like SeaMonkey

On 15/07/2016 11:36 PM, David H. Durgee wrote: Marisa Ciceran wrote: I have Seamonkey 2.40 installed and am a Chase Bank customer having experienced the same problems with login as others who have described it in detail. As of today (?), Chase Bank no longer gives a warning. Instead, it

Re: Chase Bank doesn't like SeaMonkey

Test with User Agent from Microsoft Internet Explorer 11: general.useragent.override.chase.com;Mozilla/5.0 (Windows NT 6.1; Trident/7.0; rv:11.0) like Gecko general.useragent.site_specific_overrides;true ___ support-seamonkey mailing list

Re: Chase Bank doesn't like SeaMonkey

Marisa Ciceran wrote: I have Seamonkey 2.40 installed and am a Chase Bank customer having experienced the same problems with login as others who have described it in detail. As of today (?), Chase Bank no longer gives a warning. Instead, it refuses to permit any Seamonkey login, including at

Re: Chase Bank doesn't like SeaMonkey

On 7/14/2016 9:44 PM, Marisa Ciceran wrote: I have Seamonkey 2.40 installed and am a Chase Bank customer having experienced the same problems with login as others who have described it in detail. As of today (?), Chase Bank no longer gives a warning. Instead, it refuses to permit any Seamonkey

Re: Chase Bank doesn't like SeaMonkey

I have Seamonkey 2.40 installed and am a Chase Bank customer having experienced the same problems with login as others who have described it in detail. As of today (?), Chase Bank no longer gives a warning. Instead, it refuses to permit any Seamonkey login, including at

Re: Chase Bank doesn't like SeaMonkey

Rick Merrill wrote: On 6/30/2016 6:46 AM, Desiree wrote: On 6/28/2016 9:07 PM, 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

Re: Chase Bank doesn't like SeaMonkey

On 7/7/2016 5:31 PM, Lemuel Johnson wrote: > On 7/6/2016 9:41 AM, WaltS48 wrote: >> On 06/29/2016 03:07 AM, 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

Re: Chase Bank doesn't like SeaMonkey

On 7/6/2016 9:41 AM, WaltS48 wrote: On 06/29/2016 03:07 AM, 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

Re: Chase Bank doesn't like SeaMonkey

On 6/30/2016 6:46 AM, Desiree wrote: On 6/28/2016 9:07 PM, 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

Re: Chase Bank doesn't like SeaMonkey

On 06/29/2016 03:07 AM, 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

Re: Chase Bank doesn't like SeaMonkey

On 7/1/2016 7:25 AM, Ed Mullen wrote: On 7/1/2016 at 9:11 AM, J. Weaver Jr.'s prodigious digits fired off: Ed Mullen wrote: No, the best solution is to walk into your local branch of Chase and tell them that you are moving all of your accounts to Bank Of America because their Web site is

Re: Chase Bank doesn't like SeaMonkey

On 7/1/2016 7:48 AM, Felix Miata wrote: > Ray_Net composed on 2016-07-01 16:23 (UTC+0200): > 1. They don't care ... about one leave. 2. It's a fact that SEAMONKEY is 99% of the time NOT detected and recognized by webmasters ...Do not put your head in the sand like ostriches

Re: Chase Bank doesn't like SeaMonkey

Ray_Net wrote: Daniel wrote on 01/07/2016 11:42: "Do not put your head in the sand" They will never know about SeaMonkey (and other compliant Browsers) unless *WE* make them aware of it!! Yes, but they do not want to increase the list of browsers they support In that case, they

Re: Chase Bank doesn't like SeaMonkey

Ray_Net composed on 2016-07-01 16:23 (UTC+0200): 1. They don't care ... about one leave. 2. It's a fact that SEAMONKEY is 99% of the time NOT detected and recognized by webmasters ...Do not put your head in the sand like ostriches are. "Do not put your head in the sand" They will never

Re: Chase Bank doesn't like SeaMonkey

J. Weaver Jr. wrote on 01/07/2016 15:11: Ed Mullen wrote: No, the best solution is to walk into your local branch of Chase and tell them that you are moving all of your accounts to Bank Of America because their Web site is broken. THAT is what will get their attention. Money talks,

Re: Chase Bank doesn't like SeaMonkey

On 7/1/2016 at 9:11 AM, J. Weaver Jr.'s prodigious digits fired off: Ed Mullen wrote: No, the best solution is to walk into your local branch of Chase and tell them that you are moving all of your accounts to Bank Of America because their Web site is broken. THAT is what will get their

Re: Chase Bank doesn't like SeaMonkey

Daniel wrote on 01/07/2016 11:42: On 1/07/2016 3:35 PM, Ray_Net wrote: Ed Mullen wrote on 01/07/2016 05:39: On 6/30/2016 at 3:20 PM, Ray_Net's prodigious digits fired off: Daniel wrote on 30/06/2016 14:04: On 30/06/2016 5:09 PM, Ray_Net wrote: Daniel wrote on 29/06/2016 11:34: On

Re: Chase Bank doesn't like SeaMonkey

Ed Mullen wrote: No, the best solution is to walk into your local branch of Chase and tell them that you are moving all of your accounts to Bank Of America because their Web site is broken. THAT is what will get their attention. Money talks, especially when it walks. Assuming the local

Re: Chase Bank doesn't like SeaMonkey

On 1/07/2016 3:35 PM, Ray_Net wrote: Ed Mullen wrote on 01/07/2016 05:39: On 6/30/2016 at 3:20 PM, Ray_Net's prodigious digits fired off: Daniel wrote on 30/06/2016 14:04: On 30/06/2016 5:09 PM, Ray_Net wrote: Daniel wrote on 29/06/2016 11:34: On 29/06/2016 5:07 PM, Mark B wrote: Chase

Re: Chase Bank doesn't like SeaMonkey

Ed Mullen wrote on 01/07/2016 05:39: On 6/30/2016 at 3:20 PM, Ray_Net's prodigious digits fired off: Daniel wrote on 30/06/2016 14:04: On 30/06/2016 5:09 PM, Ray_Net wrote: Daniel wrote on 29/06/2016 11:34: On 29/06/2016 5:07 PM, Mark B wrote: Chase Bank recently updated their websites, and

Re: Chase Bank doesn't like SeaMonkey

On 6/30/2016 at 3:20 PM, Ray_Net's prodigious digits fired off: Daniel wrote on 30/06/2016 14:04: On 30/06/2016 5:09 PM, Ray_Net wrote: Daniel wrote on 29/06/2016 11:34: On 29/06/2016 5:07 PM, Mark B wrote: Chase Bank recently updated their websites, and now they won't allow access using

Re: Chase Bank doesn't like SeaMonkey

Daniel wrote on 30/06/2016 14:04: On 30/06/2016 5:09 PM, Ray_Net wrote: Daniel wrote on 29/06/2016 11:34: On 29/06/2016 5:07 PM, 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

Re: Chase Bank doesn't like SeaMonkey

On 6/30/2016 at 9:37 AM, WaltS48's prodigious digits fired off: On 06/30/2016 08:59 AM, J. Weaver Jr. wrote: Mason83 wrote: Why do you have to remember every time SM updates? Just set Firefox/66.6 and be done with it? :-) There was some _other_ site (CRS, at the moment) that was actually

Re: Chase Bank doesn't like SeaMonkey

On 06/30/2016 08:59 AM, J. Weaver Jr. wrote: Mason83 wrote: Why do you have to remember every time SM updates? Just set Firefox/66.6 and be done with it? :-) There was some _other_ site (CRS, at the moment) that was actually doing range checking to block that kind of workaround. -JW I

Re: Chase Bank doesn't like SeaMonkey

Mason83 wrote: On 29/06/2016 20:13, 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

Re: Chase Bank doesn't like SeaMonkey

On 30/06/2016 5:09 PM, Ray_Net wrote: Daniel wrote on 29/06/2016 11:34: On 29/06/2016 5:07 PM, 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.

  1   2   >