Do not search for `www.<something>` strings
Categories
(Firefox :: Address Bar, defect, P2)
Tracking
()
People
(Reporter: Gijs, Assigned: daisuke)
References
Details
Attachments
(1 file)
It's a little surprising that for incomplete domains that are clearly domains because they start with www.
(which, without much evidence, I hypothesize people still use frequently...), we now search. It would seem more natural to complete with .com or similar, rather than potentially expose history to the search engine.
Comment 1•8 months ago
|
||
(In reply to :Gijs (he/him) from comment #0)
It's a little surprising that for incomplete domains that are clearly domains because they start with
www.
(which, without much evidence, I hypothesize people still use frequently...), we now search. It would seem more natural to complete with .com or similar, rather than potentially expose history to the search engine.
If the domain is known we autofill, but if it's not known it's not trivial. I think it would be fine to add the "starts-with-www." heuristic and refuse to search, but also completing may not be trivial or expected (completing www.site to www.site.com may be wrong if site is an intranet host). I'd rather just visit and show a not found error page.
Updated•8 months ago
|
Updated•3 months ago
|
Assignee | ||
Updated•2 months ago
|
Comment 2•2 months ago
|
||
Just to clarify, I think this can be fixed in uriFixup, if something starts with www. it should not do a keywordLooup.
Assignee | ||
Comment 3•2 months ago
|
||
I thought the same thing!
Thank you very much for your advice!
Assignee | ||
Comment 4•2 months ago
|
||
Pushed by dakatsuka.birchill@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ef9cec5140c9 Handle 'www.<something>' as a URI. r=mak
Comment 6•2 months ago
|
||
bugherder |
Updated•2 months ago
|
Description
•