77052 - Autocomplete should include unvisited file:/// URLs

Status: NEW

(SeaMonkey :: Autocomplete, enhancement)

Description

[Cesar Eduardo Barros]

When typing a file:/// URL in the URL bar, the autocomplete could list the
available files/directories in the disk, like a shell's tab completion. Of
course, it should only descend in a directory after the slash has been entered.

Comment 1

[Danny Colascione]

Ok, I just tried two builds in addition to mine. Both were slower. 

I tried today's (4/21) gcc build and the normal build. Both were also slow on my
system, although my build with -O3 -march=i586 was faster. In light of this, I
doubt it has anything to do with compiler options.

Comment 2

[Danny Colascione]

Oops, wrong bug.

Comment 3

[timeless]

I'm trying to decide if this would be consistent or inconsistent with our 
behavior in other places.

Here are the behaviors i know of:
http:// history based
mailto/ldap directory based
ftp:// i'm guessing we handle this as history based. although we could probably 
handle this as directory based.
gopher:// i'm guessing we handle this as history based. 

news: if we do this, we probably do this directory based.
[reassigning to networking: file to get some feedback]
bryner was working on the file picker where I think people have asked for the 
same feature.

w2k msie5.5 system url bar handles file and ftp as both history and directory, 
eg:
typing ftp://ftp.mozilla.org/p (after having visited certain pieces) gives me a 
history display
typing ftp://ftp.mozilla.org/pub/ (pausing before and after typing the trailing 
/) gives me a directory display.
once I'm in directory mode, you generally stay in it.

file:/// and c:\ [well, if i had a c:\] are not treated the same.  file:/// 
lasts as history like ftp:///, but c:\ flips to directory much faster.  <-- 
This is very hard to explain, sorry.

Comment 4

[Bradley Baetz]

Valid feature request -> confirming. Also moving to default owner/QA, which I
guess timeless meant to do.

Comment 5

[Pierre Chanial]

This bug is (chronologically) a bug of bug 45588 but this one has more insights.

Comment 6

[benc]

qa to me -qawanted.

I'm inclined to make this a dupe of that bug.

So what you are looking for w/ is sort of like Linux style (I know it's actually 
a shell, just not which one) tab-to filename completion...? 

(I grew up on csh, so I'll file a separate bug asking for the escape key...)

Comment 7

[Doug Turner (:dougt)]

to autocomplete owner.

Comment 8

[Jesse Ruderman]

*** Bug 45588 has been marked as a duplicate of this bug. ***

Comment 9

[:deanis74]

In order for bug 45588 to be a dupe of this, we'd have to get rid of the "tab
completion" requirement.

Comment 10

[Jesse Ruderman]

What the Tab key does in url bar autocomplete is covered by other bugs and
shouldn't depend on whether you're completing visted http urls or unvisited
local filenames.  Updating summary.

See also bug 97031, autocomplete should complete typed URLs beginning with /
(Linux) or c:\ (Windows) against known URLs beginning with file:.

Comment 11

[Cesar Eduardo Barros]

I never said it should use the tab key... I just said it should behave like the
tab key in a shell (which does filename autocomplete). Using the tab key for it
would be stupid.

Comment 12

[Jesse Ruderman]

Sorry for reading too much into the old summary, and I'm glad we agree on the
new one :)

Comment 13

[Matthias Versen [:Matti]]

*** Bug 150402 has been marked as a duplicate of this bug. ***

Comment 14

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 15

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 16

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 17

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 18

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614