Closed
Bug 10957
Opened 25 years ago
Closed 25 years ago
[FEATURE] Auto-complete URL entry
Categories
(SeaMonkey :: UI Design, defect, P1)
SeaMonkey
UI Design
Tracking
(Not tracked)
VERIFIED
FIXED
M17
People
(Reporter: don, Assigned: radha)
References
Details
(Whiteboard: [nsbeta2+] 5/16)
Updated•25 years ago
|
QA Contact: beppe → cpratt
It would be great if you could implement this as a combination of what NS 4.x
and IE 5.0 does. I would like it so when you start to type in a URL, it brings
up a small window underneath the location bar with all the matches for what you
have so far typed in (like IE 5.0), as well as the NS 4.x behavior of suggesting
the closest match in the URL bar. This allows you to choose one of the
suggested matches, from the list, overriding what the program chooses as the
closest URL match.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M15 → M17
Assignee | ||
Comment 4•25 years ago
|
||
Checked in code. The popup menu that s'd come up when there are multiple matches
doesn't work because of a bug in the autocomplete widget. There is a bug for it
assigned to ducarroz. I'm tracking that. But urlbar autocomplete component does
what it has to do to support multiple matches. The closest match will appear by
default in the urlbar with the autocompleted part highlighted.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 5•25 years ago
|
||
I'm reopening this since the code was backed out. When it goes back in, we can mark this fixed again and I can test it.
changing QA to me.
Status: RESOLVED → REOPENED
QA Contact: cpratt → claudius
Resolution: FIXED → ---
Comment 6•25 years ago
|
||
submitting for nsbeta2, this is an explicit feature requirement for nsbeta2.
radha, could you list the bug number for the autocomplete widget bug that's blocking this? Or I guess
it's really a dependency
Keywords: nsbeta2
Updated•25 years ago
|
Whiteboard: [nsbeta2+] 5/16
Comment 7•25 years ago
|
||
[nsbeta2+] will take if done by 5/16
Assignee | ||
Comment 9•25 years ago
|
||
I have re-enabled autocomplete in urlbar. Please note that you need something in
your urlbar history for autocomplete to take effect. If there is nothing in the
history, there is nothing for the autocomplete implementation to look up to.
Also, urlbar history is not persistent at this time. Some improvements could be
done on how urls are autocompleted. I'm aware of some and are working on it. For
the rest open bugs. In my tree, the search button seemed to behave properly
after the autocomplete was enabled. Not sure how it will behave in opt builds.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•