Closed Bug 759179 Opened 12 years ago Closed 12 years ago

You cannot edit your search in the search bar - address bar

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: filippo1, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20100101 Firefox/12.0
Build ID: 20120420145725

Steps to reproduce:

1. open the browser
2. type a search in the address bar
3. press the search button or icon to fire the search
4. tap the search bar / address bar again to edit the query


Actual results:

the words of the query have been replaced with the url of the search engine.
You can enter a new query from scratch by deleting the address, but you cannot edit the previous query, for example adding more words


Expected results:

the keywords of the search should have been persisted and should be available for editing. pressing the search button / icon should fire the new query.
Note: imho changing the meaning of an element on the UI implies changing its graphical appearance
OS: Windows XP → Android
Hardware: x86 → ARM
I doubt we would ever want to hide the current URL (i.e, a full Google search query) in replacement for showing what you have queried in the address-bar. This is probably a Wont-Fix, but I am adding Ian/Madhava for any further thought.
It's an interesting idea, certainly, but I worry about returning people into inconsistent states when they tap on the URL bar. Plus we already hide the URL in favor of the title when a page is loaded, so tapping the URL bar is the only time people can ever interact with a URL. 

If people want to tweak search queries, they are probably better off doing this from within specific search providers like google.com anyway, rather than the url bar of the browser.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.