Closed Bug 246532 Opened 21 years ago Closed 19 years ago

After minutes, location bar fails to auto-complete protocol. Over time, it fails entirely.

Categories

(SeaMonkey :: Autocomplete, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: splisken06, Unassigned)

Details

(Keywords: regression)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031007 Build Identifier: Every version of Mozilla for the OS X since 1.6 has had this problem. After about 15 minutes, putting a URL in the location bar will produce no result. It will only work if I add the http://. After that has happened, if I submitted any forms, the whole browser would be stuck because the Security Alert would appear and clicking either button would have no result. I finally shut off the security alert with 1.7rc3 and form submission went through. But, after leaving the browser open for a few hours and coming back to it, even adding the http:// to a URL in the location bar has no effect. And if I try to use the "Open Web Location ..." window, the whole thing hangs because it requires a form submission acknowledgement that hangs. I'm still using 1.5 which does not have this problem. It has been this way on Jaguar and Panther. It doesn't happen on the Windows versions (which I use at work). Reproducible: Always Steps to Reproduce: 1. Start up browser 2. Wait 15 minutes 3. Input URL in location bar without protocol 4. Submit a form Expected Results: Inputting a URL should auto-complete the protocol. Form submissions should be able to have a security warning without hanging permanently.
splisken06@email.com, can you reproduce this problem with a new Mozilla user profile?
Assignee: general → nobody
Severity: critical → normal
Component: Browser-General → XP Apps: Autocomplete
Keywords: regression
QA Contact: general
Product: Core → Mozilla Application Suite
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/
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: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.