1307086 - Please restore keyword.URL functionality

Status: RESOLVED WONTFIX

(Firefox :: Address Bar, defect)

Description

[JDev]

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
Build ID: 20160922113459

Steps to reproduce:

Attempted to use the location bar for "I'm feeling lucky" style results.


Actual results:

Landed on Google's search results page so it could display ads before it forwarded me on to the top result.


Expected results:

It should have just taken me to the top result without wasting time loading the Google results page.

Here's the problem as it relates to firefox:  because of the removal of user control, namely the keyword.URL key, users no longer have a method by which to change the location bar search to something other than Google without abandoning the service entirely by changing default search providers.  (ie: I would like to be able to maintain google for search bar results while changing it for location bar results)

Comment 1

[JDev]

and now I'm really confused... I took the step of changing default search providers yet location bar search remains on Google?

Comment 2

[Liviu Cirdei]

(In reply to JDev from comment #1)
> and now I'm really confused... I took the step of changing default search
> providers yet location bar search remains on Google?

I couldn't reproduce this. If I change the default search engine it changes on location bar accordingly.

Panos, do you have any thoughts on this?

Comment 3

[Panos Astithas (he/him) [:past] (please ni?)]

I'm afraid restoring keyword.URL is not going to happen. If anything, we are interested in making the search experience for our users simpler, not more complex. That being said, in Nightly we have one-off search buttons in the awesomebar too (apart from the search bar), so you can select a search engine other than the default any time you want "without abandoning the service entirely", as you put it. We are holding this feature from riding the trains until some bugs have been ironed out.

Comment 1 seems to be about a separate issue that I can't reproduce. If you can get some specific steps to reproduce, please file a new bug.