Closed
Bug 296355
Opened 20 years ago
Closed 20 years ago
"Accept" button for accepting terms and conditions at a banking site doesn't work with FireFox
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: moc, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
FYI, the technician for online banking at Washingtom Mutual says that my problem
(I clicked on "Accept" in FireFox, for terms and conditions, and I was sent back
to the login page rather than being allowed to proceed... over and over again)
was due to using FireFox. He recommended that I try IE. I did, IE worked where
FireFox didn't. He said that the IE trick was working for everybody who had the
problem who had been using FireFox.
Reproducible: Always
Steps to Reproduce:
1.log on after establishing online identity but before completing process
2.click on <Accept> when presented with accept-or-go-to-hell account use terms
and restrictions
3.
Actual Results:
end up back at log in (but not if Microsoft IE is used)
Expected Results:
Should have go on to show me what was in my bank account.
Comment 1•20 years ago
|
||
Is this in a password protected area of the site? Could you provide the URL of
the page where you experience this problem please?
Comment 2•20 years ago
|
||
WFM, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050601
Firefox/1.0+
(In reply to comment #1)
> Is this in a password protected area of the site? Could you provide the URL of
> the page where you experience this problem please?
I'd sure like to help, but yes, it's a page that comes up only once during the
sign-up procedure for setting up an online account. Once the user has set up the
online account that page never comes up again. Even if I had thought to copy the
URL and had given it to you, I suppose that there would be a likelihood that
there would be re-direction back to the log-on page before you could access the
page (because it's a structured session, not random access).
The log-on page is at https://online.wamu.com/logon/logon.asp?dd=1 .
Perhaps the only way that you could get to the page with the terms and
conditions and the <Accept> button in question would be to try to set up an
online account yourself... or, to find someone in your organization who has a
WAMU account but who hasn't yet created online access.
I'm glad that you're on the ball and interested.
Comment 4•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 5•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•