Open Bug 96700 Opened 24 years ago Updated 3 years ago

Location bar autocomplete should offer "base" server address first (should favor top-level domain/URLs)

Categories

(SeaMonkey :: Autocomplete, enhancement, P4)

Product:
SeaMonkey
Component:
Autocomplete
Type:
enhancement

Tracking

(Not tracked)

Status:
REOPENED
Milestone:
Future

People

(Reporter: Tony.Tovar, Unassigned)

References

Details

If I have previously followed a link to a particular sub-page of a web-site, and I remember the web-site -- but don't care about the original sub-page -- I would like the AutoComplete to offer the home-page as the first option. For example, if I've previously browsed to: - www.zdnet.com/eweek/stories/general/0,11011,2807174,00.html After typing "www.z" I would like AutoComplete to offer me two options: - www.zdnet.com - www.zdnet.com/eweek/stories/general/0,11011,2807174,00.html
yep! I would totally agree with you on this one. The only reason I didn't add this bug is because I think it's covered by another bug report. I haven't found it though :( I'll post back if I find the duplicate (if any)
Hmm.. i'm sorry I can't seem to hunt it down. Either it doesn't exist, or bugzilla ate my search results. I'll mark it as "NEW" unless someone finds a duplicate. However, a related but, (but probably not a duplicate) would be bug 77935.
Status: UNCONFIRMED → NEW
Ever confirmed: true
According to Joe Hewitt, all sorting issues about autocomplete go in bug 78270
This is more than a sorting request. I would also like the Autocomplete function to add the base hostname entry (to go to the homepage) even if you've never loaded it before.
see bug 93099
making a dupe of 78270 *** This bug has been marked as a duplicate of 78270 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
This is NOT a duplicate. It is only tangentially related to sort order. Please remove the Duplicate status... ---------------- What I am asking is that the base hostname be added (i.e., point to the homepage) EVEN IF it was never viewed previously. This is an new, from-scratch Autocomplete entry and not simply a sorting issue.
Is bug 78270 a tracking bug? I read bug 93099 and it made a suggestion that is similar to mine, i.e., pressing TAB will jump to the first "/" in the suggested URL (rather than inserting the entire URL). Bug 93099 was then marked as duplicate to bug 78270, but I don't see anything in bug 78270 that specifically identifies this goal (easy access to base hostname)...
I'd agree, Tony. Marking reopened per request of reporter, and because I would agree this IS a separate bugger.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
XP:Autocomplete
Assignee: asa → hewitt
Status: REOPENED → NEW
Component: Browser-General → XP Apps: Autocomplete
QA Contact: doronr → blakeross
bug 78270 is a tracking bug. I sum-up the issues about sorting and splitting URL in 78270. I agree its name should be changed to be more general. I have requested it.
Status: NEW → ASSIGNED
Priority: -- → P4
Target Milestone: --- → Future
I don't think that this bug is an enhancement, but the fix of a partly broken feature. Right now the adress Mozilla offers me when I type "www.amazon." is one of an outdated session, but not just simply "www.amazon.com". This behaviour is quite absurd and makes the autocomplete feature partly senseless IMO. Therefore I suggest to change severity to normal at least.
*** Bug 125007 has been marked as a duplicate of this bug. ***
Let me note a few things, I marked the bugreport I submitted as duplicate of this, since it comes pretty close, except mine didn't add the wish for seperating the base level domain from an pasted URL in the URL bar for autocompletion. Mine hightlighted the fact that some base level domains you enter in the URL bar sometimes do not get stored. [e.g. www.google.com] But I have to say I like the ability to seperate the base level domain from the URL as well, for future autocompletion.
changing qa to claudius.
QA Contact: blaker → claudius
Keywords: mozilla1.0
adding self to cc list
Blocks: 140404
At the very least, autocomplete should offer you the shortest URL you have visited that matches what you have typed so far. I hate that I can type news.y and Mozilla autocompletes something like http://news.yahoo.com/news?tmpl=story2&cid=574&ncid=721&e=2&u=/nm/20020825/wl_nm/weather_china_floods_dc_54 when all I wanted was news.yahoo.com. It makes autocomplete pretty useless unless you routinely revisit only the longest URL's in your history.
Come on guys, this is practically a BUG not an enhancement. It makes the history largely useless as comment #12 says. I have *exactly* this problem with www.google.com all the time - it matches an old search, not the base domain, because google redirects me to www.google.co.nz so that www.google.com never gets into the history.
bug 142190 is similar, if not a duplicate.
*** Bug 142190 has been marked as a duplicate of this bug. ***
This bug is not plattform specific, changing settings.
OS: Windows NT → All
Hardware: PC → All
There's some clearer discussion of this issue over in bug 175725, which is a superset of this bug.
Keywords: mozilla1.0
adding self to CC i would say bug 164945 is a dupe
I find this bug to be the single biggest problem with using Mozilla (currently Firefox 0.8). It appears not to have been touched in about a year. I believe that 128341, 109758, 164945, 175725 are all duplicates of the same problem. I cannot tell if any are active, but it appears that they are not. Can anyone (Joe Hewitt?) consolidate these, and better yet, speak to a fix? I don't want to change priorities for someone else's work, but I would call this a "normal" severity problem.
Since no one has comment recently, let me just add that this 'issue' is still present in Firefox 1.0-PR on WinXP. Sorry for the spam.
Product: Core → Mozilla Application Suite
See also the Firefox version of this: Bug 240397 "Location-Bar auto-complete should favor top-level URLs (should put top-level domain at the top of the list)".
Assignee: hewitt → nobody
Status: ASSIGNED → NEW
QA Contact: claudius
Summary: Autocomplete should offer "base" server address first → Location bar autocomplete should offer "base" server address first (should favor top-level domain/URLs)
*** Bug 128341 has been marked as a duplicate of this bug. ***
*** Bug 164945 has been marked as a duplicate of this bug. ***
This bug pre-dates Firefox and still has Product="Mozilla Application Suite". Should it be updated to say Product="Firefox"? It doesn't seem like a complicated thing to implement and it has quite a few votes and dupes.
No, this still affects the suite as well. Probably Core / XP Toolkit/Widgets.
Bug 240397 c26 says that the autocomplete code is different between the suite and firefox, hence it wasn't listed as a dupe of this one. No point in reassigning it imo.
No comment in over two years. Firefox autocomplete has been changing quite a lot in the past few months, and I expect that within the next year, SeaMonkey-trunk will be ported to that same code. I could be wrong though.
I hope someone can do the work to make us use much of the code that Firefox 3 uses for location bar autocomplete (now dubbed "awesomebar" there), yes. We won't become a clone of Firefox, but I think they way results are fetched and ordered is good in their code. I for myself don't like the way results take up more than one line in the dropdown though ;-)
(In reply to comment #33) > I hope someone can do the work to make us use much of the code that Firefox 3 > uses for location bar autocomplete (now dubbed "awesomebar" there), yes. We > won't become a clone of Firefox, but I think they way results are fetched and > ordered is good in their code. I for myself don't like the way results take up > more than one line in the dropdown though ;-) > I suppose the aesthetics won't be too hard to work out -- "if and when". See also bug 101642 which I expect would (will?) be automagically fixed by porting the awesomebar to SeaMonkey.
QA Contact: autocomplete
bug 382187 will only make us use the history part of places, so bookmarks won't show up right away with that. But given that top-level domains are usually visited more often then pages underneath them, this issue will much improve with that. Effectively, that switch to places will also make this a dupe of bug 240397.
Similar bug for Firefox: bug 240397.
https://hg.mozilla.org/mozilla-central/rev/100d59736c77 https://hg.mozilla.org/mozilla-central/rev/da3d74c47e8e
Assignee: nobody → mihaela.velimiroviciu
Status: NEW → RESOLVED
Closed: 24 years ago → 11 years ago
Resolution: --- → FIXED
Resolution caused by typo. Reverting.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: mihaela.velimiroviciu → nobody
You need to log in before you can comment on or make changes to this bug.