David H. Durgee wrote:
A Williams wrote:
David H. Durgee wrote:
Marisa Ciceran wrote:
Same problem here as of the start of this weekend. I've been on the
phone several times with Chase support about this and this time the
agent I spoke to said he sent a note to their compatibility developers.
I am on 64-bit Windows 7 Pro on on ASUSI7 4790k processor.
Marisa
NoOp wrote:
On 12/08/2014 10:21 AM, Lemuel Johnson wrote:
On 12/8/2014 10:52 AM, NoOp wrote:
On 12/08/2014 05:23 AM, J. Weaver Jr. wrote:
Ken Rudolph wrote:
Ron wrote:
Just got the 2.31 upgrade & now I can't log in to my account on
chase.com I hit logon & it just reloads the log on page. Works in
IE and
Seamonkey 2.30
Same thing happening here. This is frustrating. Can I go back to
Seamonkey 2.30? Or maybe spoof the browser to firefox (which
used to
work when bank sites didn't accept SeaMonkey)?
Same problem here: worked great with IE & 2.30, not at all with
2.31.
<sigh> Is there a Bugzilla entry for this yet? -JW
<https://bugzilla.mozilla.org/show_bug.cgi?id=109471>
( Unable to login at chase.com due to NS_ERROR_FAILURE (SeaMonkey
only))
and for reference, here is a previous one that was fixed last year:
<https://bugzilla.mozilla.org/show_bug.cgi?id=924025>
(Unable to log in at chase.com)
I believe that's actually
https://bugzilla.mozilla.org/show_bug.cgi?id=1094714
Lem Johnson
You are correct - thanks for the catch!
Gary
Well, that is enough reason to hold back from upgrading for me! I have
a Chase account, so until this is fixed or there is a work-around this
one is a show-stopper.
Dave
Well, the cause is now known, and it *is* possible to access the site
using SM 2.31. Comment 21 in the 1094714 bug report has it.
The steps recommended by Phillip Chee solved the problem for me (Ken
Jarman), Thanks Phillip:
1. Restart SeaMonkey. DO NOT go to chase.com YET
2. Open the Error Console (CTRL-SHIFT-J)
3. Evaluate:
Components.utils.import("resource://gre/modules/Webapps.jsm");
4. Try to login to chase.com
One hell of a workaround.
Is this a one-time fixes-it-forever work-around or one that needs to be
repeated every time you restart SeaMonkey? Is the restart necessary or
just cleaner?
I am assuming now that it is identified it will be fixed in the next
release, correct? I doubt that Chase is the only site impacted by it.
Dave
I'm assuming it is an each-time-you-restart-seamonkey job.
What it really means is that the developers care *and* know what the
problem is. I'd expect the next version of Seamonkey to be fixed.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
