Closed Bug 156790 Opened 22 years ago Closed 10 years ago

secu.org - Unable to submit secure webpage form data

Categories

(Web Compatibility :: Site Reports, defect, P2)

x86
All

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: javaman67, Unassigned)

References

()

Details

(Whiteboard: [bank])

Attachments

(1 file)

Any nightly builds of Mozilla in Linux since build 2002052918 will not send the
data on the above URL.  Build 2002052918 works fine.  This is my bank login website.
PSM issue maybe? (personal security manager) Is not a default on linux like on
other platforms.
Confirming on build 2002-07-02-04-trunk. On windows 98 I am redirected to a page
saying that my login is invalid, and on linux it only changes the text in the
Account# text field to "Loading"
Status: UNCONFIRMED → NEW
Ever confirmed: true
 Yes this is exactly what's happening......"on linux it only changes the text in
the Account# text field to "Loading".  

Thanks,
Brian Craft
javaman67@acd.net
Attached file testcase
I am very confused how this works at all on IE and on Windows branch, but on
both windows and linux trunk builds the form is not submited. The problem here
seems to be that in one case the javascript submit() function calls the
onsubmit handler and in the other it does not... When it does call the onsubmit
the handler returns false (There is actually no way for it to return true!!!)
so the form submission is canceled. When it does not call the event handler,
the form is submitted and the request is processed like it should. I dont know
what is the right behaviour, but I think I've seen this bug somewhere, I'll
look for it.
Keywords: testcase
OS: Linux → All
vladimir, are you seeing that testcase act differently on Windows and Linux?  
Or just the original page?

Note that this behavior will be different between quirks and standards mode.
On windows branch it is "passing" and on windows trunk it is failing just like
on linux trunk.
That dupe was bug 45190, its actually reverse of this. It was a bug I filed, but
it was marked invalid for backward compatibility, and compatibility with IE.
Based on that resolution the behaviour experienced in the trunk builds is a bug.

The javascript submit() method should not run the onsubmit event handler for the
form.
Priority: -- → P2
Keywords: regression
Vladimir, the decision of bug 45190 was reversed in strict mode only (see bug
144534).  Your testcase is in strict mode.

*** This bug has been marked as a duplicate of 155453 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
oh, cool, that explains it.
Status: RESOLVED → VERIFIED
This should be evengelised to the bank...
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
moving to evangelism
Component: Form Submission → US Banks
Product: Browser → Tech Evangelism
Version: other → unspecified
to banks owner.
Assignee: alexsavulov → aruner
Status: REOPENED → NEW
Keywords: regression, testcase
QA Contact: vladimire → bclary
This has started to happen to me with my bank:
https://online.lloydstsb.co.uk/customer.ibc
I presume it's the same bug? Can someone confirm it for me?
Either way it doesn't as of build 2002071722 on linux
and it's going to be a real pain if I have to wait for 
them to fix their web page. Hmph. 
Ignore the above comment, the LloydsTSB site works again with later builds (see
bug 155453 comments 18-23.
Summary: Unable to submit secure webpage form data → secu.org - Unable to submit secure webpage form data
Whiteboard: [bank]
SPAM: New Components
Assignee: aruner → english-us
Component: US Banks → English US
QA Contact: bc → english-us
one of the best references/recommendations I've found for encouraging financial institutions to support firefox is located at bankers on-line web site 

http://www.bankersonline.com/security/security_browserthreat070204.html 

It was written in 2004 during the download.ject attack, but much of it still applies today.  This is a good link to send when contacting banks.
→ ping webpb.secu.org
PING webpb.secu.org (205.178.189.131): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Assignee: english-us → nobody
Status: NEW → RESOLVED
Closed: 22 years ago10 years ago
Component: English US → Desktop
Resolution: --- → INVALID
Product: Tech Evangelism → Web Compatibility
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: