Closed Bug 76028 Opened 25 years ago Closed 25 years ago

Auto-complete does not recognize HTTP sites that start with ftp.XXXX

Categories

(SeaMonkey :: Location Bar, defect)

defect
Not set
minor

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: cafelatte, Assigned: hewitt)

References

()

Details

When visiting an HTTP version of an FTP site such as: http://ftp.mozilla.org/pub/ when you type ftp.mozilla etc and it auto-completes the rest of the address, Mozilla thinks that you are trying to visit: ftp://ftp.mozilla.org/pub/ instead of http://ftp.mozilla.org/pub/ In other words, Mozilla's auto-complete history doesn't remember which protocol the site you are visiting is using.
You could always type http://ftp ...... Why should it remember the protocol? If you visited the http:// and ftp:// version, how should it decide? I think this is better left as is.
I can confirm this is a problem. Here is a better explination: What to do: Go to: http://ftp.mozilla.org Now type: ftp.mozilla.. and let autocomplete complete the URL for you. Result: You are taken to ftp://ftp.mozilla.org Expected Result: The browser will use http://ftp.mozilla.org since this is the only way you have ever gone to this URL. Looks like autocomplete is not storing the protocol of the URL. I am not sure how it determines to use FTP as the default instead of HTTP. I want to test what would happen if an ftp server is not avaliable. I think we should store the protocol in autocomplete, this will be very important when additional protocols become common with browsers...like IRC? :)
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 2000 → All
Hardware: PC → All
Target Milestone: --- → mozilla0.9
I was so sure we had this bug filed..anyways, this mgiht go away with the patch for bug 43189.
Assignee: asa → alecf
Component: Browser-General → URL Bar
QA Contact: doronr → claudius
Target Milestone: mozilla0.9 → ---
since joe is busily working to complete the new autocomplete, I figure he may want to tackle/comment on this bug.
Assignee: alecf → hewitt
This is fixed the work being done in bug 43189.
Status: NEW → ASSIGNED
Depends on: 43189
fixed
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
This problem still exists with Milestone 0.9
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I don't think a .9 build is new enough to have the fix, check your build date. This bug is very fixed in a 2001050808 build. marking FIXED.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
and VERIFIED Fixed (with 2001050808 builds)
Status: RESOLVED → VERIFIED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.