Closed
Bug 611701
Opened 14 years ago
Closed 13 years ago
Selecting a search provider too quickly does not execute the search of a query
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(fennec-)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
fennec | - | --- |
People
(Reporter: aaronmt, Unassigned)
Details
Mozilla/5.0 (Android; Linux armv7l; rv:2.0b8pre) Gecko/20101112 Firefox/4.0b8pre Fennec/4.0b3pre When no results from ones query are found from searching in the location bar, Fennec offers a variety of search providers that one can tap in order to perform the search on that selected provider. When one conducts a search using one of the search providers too quickly, Fennec will not execute the search using the provider. The search that one expects to be performed does not happen, merely, the awesome screen closes and the page remains blank. Note: I have encountered this primarily through voice search. STR 1. Tap the voice icon on your device's virtual keyboard 2. Mention anything, Android may or may not present a clarification of what you meant. If so, tap any of the results in the prompt. 3. The search provider listing should display 4. As soon as that happens, tap the first provider which is Google ER: Fennec conducts the search through google. AR: Awesomescreen closes, no search is performed. Tested: Motorola Milestone, Nexus One
Reporter | ||
Updated•14 years ago
|
Summary: Selecting a search provider too quickly does not execute the search → Selecting a search provider too quickly does not execute the search of a query
Updated•14 years ago
|
Flags: in-testsuite?
Flags: in-litmus?
Updated•14 years ago
|
tracking-fennec: --- → ?
Comment 1•14 years ago
|
||
I haven't been able to reproduce this and finkle says he's never seen it
tracking-fennec: ? → 2.0-
Comment 2•13 years ago
|
||
Aaron - still happens for you?
Reporter | ||
Comment 3•13 years ago
|
||
Nope.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•