From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.0) Gecko/20020530 BuildID: 2002053012 Whenever I use Mozilla 1.0 to login to a service that uses the default form submit button the site is not resolved. However, if I login to a site that uses an image for the form submit button there are no problems. Reproducible: Always Steps to Reproduce: 1.Fill in login form for the Motley Fool 2.Click on the "login" button 3. Actual Results: Pop-up window appears informing my www.fool.com could not be resolved. Expected Results: Form should be submitted and my site home page displayed.
Works for me, if I use some random login data. At least the submit button is ok. Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530; Build ID: 2002053012 Do you get forwarded after clicking on the button or does this happen before anything gets loaded? What happens if you try to log in with a wrong user name?
no blocker.. Reporter: Have you installed Mozilla over an older build ? If yes do this : uninstall mozilla, delete all files in c:\programs\Mozilla.org\Mozilla\ (but save your plugins) and reinstall mozilla. If you still see the problem try "mozilla -profilemanager" and create an additional test profile.
Severity: blocker → major
This was a first time install. Some additional information that I've found. We use a proxy here and I didn't have the Preferences/Advanced/Proxies I didn't have an SSL Proxy defined. Defining an SSL Proxy resolved the problem. My confusion though is why on a site where the submit button is an image rather than the standard form submit button the submit event worked properly without an SSL Proxy defined. I would have expected it not to work for both types. Regarding your other question: Do you get forwarded after clicking on the button or does this happen before anything gets loaded? The answer is no I don't get forwarded. The pop-up error about not being able to resolve the URL appears. Once you click OK in that dialog the pop-up goes away but you are left where you were.
-- My confusion though is why on a site where the submit button is an image rather than the standard form submit button the submit event worked properly without an SSL Proxy defined. I would have expected it not to work for both types. -- Was the page with the image also from fool.com? Or was it just some random form with no SSL connection that therefore worked with your previous proxy settings? So, if someone comes along with the right privileges, I think a STATUS: CLOSED RESOLUTION: INVALID would fit here :)
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.