Closed Bug 325306 Opened 19 years ago Closed 16 years ago

Financial institution site, regression: Dialog box won't go away, and Camino won't Quit.

Categories

(Camino Graveyard :: General, defect)

1.8 Branch
PowerPC
macOS
defect
Not set
major

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: greatnessguru, Unassigned)

References

(Depends on 1 open bug, )

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060130 Camino/1.0b2+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060130 Camino/1.0b2+

Expected result: dialog box goes away.

Actual result: dialog box pops up, then drops down again. Won't go away.

Side affect: "Camino > Quit Camino" doesn't work.

Note: Same bugs even with a valid Member Number and Password.


Reproducible: Always

Steps to Reproduce:
Enter a Member Number and Password.
Example:
Member Number (fictitious): 5528897416
Password (fictitious): fb47cr31jk

Next page will be "member Verification Error... Invalid login attempt. ...".

A drop-down error dialog box will drop down,
"Please enter a password between 4 and 8 characters long. [OK]"

Click on "[OK]".

Actual Results:  
Actual result: dialog box pops up, then drops down again. Won't go away.

Side affect: "Camino > Quit Camino" doesn't work.

Note: Same bugs even with a valid Member Number and Password.


Expected Results:  
Expected result: dialog box goes away.


Work around:
Playing with New Tab, Bookmarks > Show All Bookmarks,
and clicking that "[OK]" can make the dialog box go away.


Works fine in Deer Park, all nightlies ever tested/used, including 20060130.

Works fine in Firefox 1.0.7, "Debian package 1.0.7-1":
Debian Linux, x86, "Testing".
Impact:
Can't log in to the site, a financial institution.
I never get the invalid login *sheet*. I get the *page*, but no sheet (which I suspect is being thrown by JavaScript).

Reporter: Does the 1/31 Camino nightly have the same problem?

cl
(In reply to comment #2)
> I never get the invalid login *sheet*. I get the *page*, but no sheet (which I
> suspect is being thrown by JavaScript).
> 
> Reporter: Does the 1/31 Camino nightly have the same problem?
> 
> cl

Camino "2006013104 (v1.0b2+)" still has the problem I reported of the error dialog box,
"Please enter a password between 4 and 8 characters long. [OK]",
not going away after clicking "[OK]".

Chris, you did not report seeing the error dialog box, clicking on "[OK]",
and the results of doing that. Therefor, I do not know if this is the "same"
problem you asked me to verify in today's nightly.

I followed the "Steps to Reproduce", the error dialog box dropped down,
I clicked "[OK]", the error dialog box did Not go away.

Chris, did you follow the "Steps to Reproduce", see the error dialog box drop down,
click on "[OK]", and see it either go away or Not go away? I thought the "Steps to Reproduce" were very clear, but you said nothing about any error dialog box...

Thank you,
Eddie Maddox
(In reply to comment #3)
> Camino "2006013104 (v1.0b2+)" still has the problem I reported of the error
> dialog box,
> "Please enter a password between 4 and 8 characters long. [OK]",
> not going away after clicking "[OK]".
> 
> Chris, you did not report seeing the error dialog box, clicking on "[OK]",
> and the results of doing that.

That's because I never *got* the error sheet. (You refer to a dialog that "drops down", which is why I'm calling it a sheet, not a dialog. A dialog is a standalone window.) It's awfully hard to click OK in a sheet that doesn't exist when I try to reproduce it.

cl
Oh, and for the record, this looks almost identical to the online banking software that Flagstar uses (with whom I've yet to have any problems with Camino or any other browser). In case that means anything to anyone else.

cl
> > Chris, you did not report seeing the error dialog box, clicking on "[OK]",
> > and the results of doing that.
> 
> That's because I never *got* the error sheet. (You refer to a dialog that
> "drops down", which is why I'm calling it a sheet, not a dialog. A dialog is a
> standalone window.) It's awfully hard to click OK in a sheet that doesn't exist
> when I try to reproduce it.
> 
> cl

Thanks for explaining that. I was used to a different terminology.

EM


Chris, I'm wondering if I need to update anything here. I keep this Mac updated with "Software Update...", but maybe we should check.

Applications > Utilities > Java has:
Java 1.3.1 Plugin Settings 10 NOV 2003
Java 1.4.2 Plugin Settings 16 SEP 2005
Mac OSX 10.3.9

Eddie

> Applications > Utilities > Java has:
> Java 1.3.1 Plugin Settings 10 NOV 2003
> Java 1.4.2 Plugin Settings 16 SEP 2005
> Mac OSX 10.3.9

I deleted "Java 1.3.1 ...".
I tried the "Steps to Reproduce" again.
I got the "Please enter a password between 4 and 8 characters long. [OK]"
drop-down little box.
I clicked on "[OK]".
The little drop-down box went up, then came back down again. It did Not go away.

Eddie
The password field has a maxlength of 8 characters, so the only way you should be able to get the warning sheet about password length is to enter a password shorter than 4 characters.
Java almost certainly has nothing to do with this. (Java and JavaScript are related in name only.)

Using Stuart's suggestion, I can get the dialog, but clicking "OK" makes it disappear. I could not get the dialog to come back on subsequent attempts; it only appeared the first time. I still don't know whether it broke the action of quitting Camino or not.

cl
We're spawning alerts recursively on the stack.
Status: UNCONFIRMED → NEW
Depends on: 300057, 303484, 304200
Ever confirmed: true
(In reply to comment #11)
> We're spawning alerts recursively on the stack.

Thanks, Simon. I've read much of "300057 303484 304200" and understand this one is hard and may not get fixed for several months. (Thankfully, all works fine in Firefox/Deer Park, so I can use those.)


However, one more funny about this:
that "Please enter a password between 4 and 8 characters long. [OK]"
error sheet drops down Even when the password Is 4-8 characters long.

Is this part of the problem due to my financial institution's server code (JavaScript?),
or is this a Camino bug, too?

Thank you,
Eddie
(In reply to comment #12)
> However, one more funny about this:
> that "Please enter a password between 4 and 8 characters long. [OK]"
> error sheet drops down Even when the password Is 4-8 characters long.
> 
> Is this part of the problem due to my financial institution's server code
> (JavaScript?),
> or is this a Camino bug, too?

This part of the problem Does happen on all of Firefox 1.0.7, Deer Park & Camino,
not just Camino alone, at least for me.

Thanks,
Eddie
Camino 1.0.RC1: Bug 325306 confirmed, still present.

Mac OSX 10.3.9, Blue G3.

Eddie Maddox
"Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1a3)
Gecko/20060526 BonEcho/2.0a3"

Worse problem.

BE hangs (infinite loop?) as soon as that drop down box drops down, and before any graphics or text gets displayed.

A definite regression from Firefox 1.5.0.3, which is usable on this (my) financial institution site.

Thank you,
Eddie
OS: Mac OS X 10.2 → Mac OS X 10.3
Product: Camino → Firefox
Version: unspecified → 2.0 Branch
dupe of bug 339359, similar symptoms, different way to reproduce?

I've only tested bug 339359 against Firefox trunk, but in fact i'm also seeing this behavior in TB branch.

So possibly we need to dupe this against bug 339359 and change "version" for that bug to branch and trunk
Eddie, are you reporting a different problem with the same site in comment 15? If so, please file a new bug. This bug is a Camino bug and should remain in that product.
Thanks, Patrick & Samuel.

I file a comment on Bug 337646 (perhaps related to Bug 339359) regarding the Bon Echo situation, and subscribed there, too, so I can test a suitable nightly when ready.


I changed this here bug back to Camino.

I tried this here bug out on Camino 1.0.1: Still There. No change.

Is this expected to be fixed in the Camino 1.0.x series? Or later?
I can test nightlies or suchlike.

Eddie
Product: Firefox → Camino
Version: 2.0 Branch → 1.8 Branch
Assignee: mikepinkerton → nobody
QA Contact: general
Camino nightly 1 AUG 2006, 3:26: No change.

BonEcho/Firefox 2 Bug 345564, Comment #9, may be related somehow.

Eddie
Camino 1.5.RC.2: fixed.

I suspect the website code was improved/corrected
sometime after Ff2 was released last OCT 2006.

Thank you,
Eddie
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Changing resolution to WORKSFORME, since we don't know what code change (if any) fixed this.
Resolution: FIXED → WORKSFORME
Reopening per comment 11, since Simon suggests there's actually a bug here.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
(In reply to comment #22)
> Reopening per comment 11, since Simon suggests there's actually a bug here.

Do we know for sure that the bug Simon mentions wasn't fixed between Feb 2006 and May 2007?  We certainly changed lots of code in that period, as did Core.
The underlying issue already has bugs tracking it, and it sounds like this specific manifestation is gone, so re-WFMing this.
Status: REOPENED → RESOLVED
Closed: 17 years ago16 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
Camino
1.6b4 (v1.8.1.13 2008032710)

I entered http://usfed.org/ in the location bar,
then proceeded to login, first with invalid PW,
then with all valid login info.

Everything worked as expected both times.

Thanks for all the work to fix this. I'm sure others, too,
are happy, though they may never know it.

Eddie Maddox
Resolution: WORKSFORME → FIXED
As explained in comment 21, WFM is the correct resolution. Please don't change resolutions that have been set by Camino developers/triagers.
Resolution: FIXED → WORKSFORME
(In reply to comment #26)
> As explained in comment 21, WFM is the correct resolution.
> Please don't change resolutions that have been set by Camino developers/triagers.

Thanks for the explanation.

At least it works now, so institution members can log in,
and get their money stuff done, as I just did.

Thanks again,
Eddie Maddox
You need to log in before you can comment on or make changes to this bug.