Closed
Bug 1321553
Opened 9 years ago
Closed 9 years ago
Non-Search Bookmark Keywords in URL Bar Incorrectly Prioritize Autocomplete
Categories
(Firefox :: Address Bar, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1124238
People
(Reporter: joshua, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20161129173726
Steps to reproduce:
1. Visit wikipedia.com.
2. Visit any other page on any other domain, and create a bookmark keyword for it with the text of "wiki".
3. Type the bookmark keyword of "wiki" into the address bar, visually verify that the top entry in the list under the address bar matches your bookmark keyword and is highlighted, then press enter.
Actual results:
In Firefox 50.0.2, wikipedia.com loads.
To make the bookmark keyword actually work, a space has to be added to the keyword, ie: "wiki " will cause the bookmarked page to load rather than wikipedia.com
Expected results:
In Firefox 49.0.2 the bookmark keyword is recognized and the associated bookmark loads.
This is the correct behavior in my opinion. Bookmark keywords are not just for searches, they are also for flat bookmarks. It shouldn't be necessary to add an extra space at the end to make them work. It is my personal belief that this change represents a regression.
The example above is just that, one example. The problem isn't limited to wikipedia or the keyword "wiki". It would also happen on google.com with a keyword of "goo" or on amazon.com with a keyword of "ama" or "amaz" or "amazo" or any other short text string that matches an domain via autocomplete.
As a side note, this regression has happened at least once before, however I cannot recall the version number when it started or when it was fixed. I think it was somewhere around the mid-40s, but I don't have solid data on that.
Updated•9 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
| Reporter | ||
Comment 2•9 years ago
|
||
I searched for 10 minutes before submitting this. Apologies for the duplicate.
You need to log in
before you can comment on or make changes to this bug.
Description
•