435230 - Typing a domain name in Awesomebar should make first result the domain's homepage

Status: RESOLVED DUPLICATE of bug 240397

(Firefox :: Address Bar, defect)

Description

[Jennifer Morrow [:Boriss] (UX)]

For example, if the user types "cnn," the first result should be http://www.cnn.com.

Currently the domain page will only be the first link if it meets the frequency/relevance criteria, so typing cnn would often give a recent article.

Comment 1

[Kai Liu]

Also see bug 430355

Comment 2

[Ihar 'Philips' Filipau]

I voted for this bug too.

Several months into Fx3 use - and Awesome Bar became quite useless in 90% of cases to me.

Somehow before, when I wanted simply to go to some web site, just start typing it's name and one of the first matches was the web site itself. Now - it is probably most frequently visited pages on this site.

For example, in my case this is price matching site. Right now I'm planning upgrade for my home PC and awesome bar is filled with pages I visited past week very often: CPU page, video card page, PMP page, etc. Now I wanted to check prices for something different - but the home page now is listed somewhere deep down the list and I need to press PgDn twice to even reach it.

Safari would always put first "www.cnn.com" when I type "cnn". After selecting from "www.cnn.com" from the list and typing "/" it would suggest as first entry next most visited part of URL e.g. "2008" (since most news start as "www.cnn.com/2008/"). In past (in Safari 1/2 - dunno about Safari 3) they used that together with inline completion. Was pretty useful and better than Mozilla's silly inline completion of the whole URL from history.

Comment 3

[Jens Müller (:tessarakt)]

@ comment #2: ACK, this is a behavior that only starts to get annoying after you have used the awesome bar for quite some time. No wonder that usability testing did not catch that.

Comment 4

[Drew Willcoxon :adw]

Dupe of 240397?  They're the same from the user's perspective but of course the awesomebar didn't exist circa 240397.  If they're not dupes maybe 240397 should be closed.

Comment 5

[Jennifer Morrow [:Boriss] (UX)]

(In reply to comment #4)
> Dupe of 240397?  They're the same from the user's perspective but of course the
> awesomebar didn't exist circa 240397.  If they're not dupes maybe 240397 should
> be closed.

Yeah, I'd call that a dupe.  I'll go ahead and dupe this one Bug 240397 has a patch.