Closed Bug 739580 Opened 10 years ago Closed 6 years ago
Don't ignore search bar keywords for inline autocomplete
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120326 Firefox/14.0a1 Firefox/14.0a1 Build ID: 20120326031149 Steps to reproduce: As described here : https://bugzilla.mozilla.org/show_bug.cgi?id=566489#c251 the new inline autocomplete mechanism doesn't recognize search bar keywords, what can lead to mismatches when the user is used to simply use it's keyword to be redirected to it's search page. Expected results: The expected behavior is to get inline autocompletion if and only if what has been typed doesn't match a search bar keyword.
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 I have tested this issue on Ubuntu 14.04 x64/x32 and Ubuntu 16.04 x64 with the latest Firefox release (47.0), the latest Nightly (50.0a1-20160615030209) and haven't managed to reproduce it. I haven't found this functionality on Nightly(14.0a1), however on the latest releases it works as expected. Can you please retest this using the latest Firefox release and the latest Nightly build (https://nightly.mozilla.org/) and report back the results? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/PNe90E).
I wish I could edit the original message and make it clearer. For the record, at that time, the inline autocomplete feature was introduced with a disruptive behavior. Say, you had a search keyword "w" for searching wikipedia, but the habit of visiting wordreference much more often. Typing w in the awesomebar would prefill it with …ordreference.com (not recognizing "w" as a keyword) and pressing enter would take you there instead of to the usual search page of wikipedia that you would have reached after the same keystrokes before. It seems that nowadays the awesomebar has been rewritten to large extents and that it now recognizes search keywords, issue closed.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.