Closed Bug 228718 Opened 22 years ago Closed 21 years ago

When loggin into Fidelity.com from this URL, the browser displays a blank page and posts "Done" in bottom left corner

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: patchrobin, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208 After logging into Fidelity.com successfully, when one clicks logout, the user will be sent to this URL: https://scs.fidelity.com/webxpress/redirectToDefaultPage.shtml When one enters the social security number and passowrd on this page and then click login, the user is sent to https://scs.fidelity.com/webxpress/redirectToDefaultPage.shtml The problem is: a blank page is displayed, and the bottom left corner shows "Done". Reproducible: Always Steps to Reproduce: 1. You have to have an account with Fidelity. Login to Fidelity. 2. Logout. 3. On the logout page, enter the login id and try to login to fidelity.com again. Actual Results: a blank page is displayed Expected Results: one should be back into the persoal homepage after logging into one's account.
I don't know if this helps you but I went to that page it was blank, but I noticed a pop-up was blocked. When I allowed the pop-up, and went to that page again, a login screen appeared (but no pop-up came up). To confirm, I went back to block the pop-up, tried page again -> blank. Allow it and try page again -> login screen. I don't have a Fidelity account so I can't help further. I just tried stuff further: Warpzilla nightly trunk 1.6b 2003121408 -> need pop-up allowed to work. Warpzilla milestone 1.5 20031017 -> need pop-up allowed to work. Warpzilla milestone 1.4.1 20031014 -> no pop-up blocked, works on the first try! Warpzilla milestone 1.3 20030313 -> no pop-up blocked, works on the first try So it seems that something happened starting with Mozilla 1.5 to change the behavior...
is this a duplicate of bug 101190?
Product: Browser → Seamonkey
anyos, can you reproduce this with a current Mozilla 1.7.5 or Firefox 1.0 build?
-> no reply Reporter, If you can reproduce this in the latest milestone or a recent (no more than 3 days old) nightly build, then re-open.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.