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 _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
