Closed Bug 1262077 Opened 10 years ago Closed 5 years ago

Search engine display order logic changes after all were set as default

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(firefox45 affected, firefox46 affected, firefox47 affected, firefox48 affected)

RESOLVED INCOMPLETE
Tracking Status
firefox45 --- affected
firefox46 --- affected
firefox47 --- affected
firefox48 --- affected

People

(Reporter: u549602, Unassigned)

Details

Environment: Beta Device: Sony Xperia Z2 (Android 5.0.2); Build: Nightly 46.0b8 (2016-04-04); Steps to reproduce: 1. Go to Settings-Search 2. Set 3 different search engines as default 3. Observe the Search engine display order 4. Set each of the search engines as default 5. Observe the Search engine display order Actual result: Step 3 : Last used search engine is moved one position down in the list Step 4 : After all were set as default, when setting a new search engine from the list, the other are displayed alphabetically. For further details please check : https://www.youtube.com/watch?v=9m2CkUxsPok&feature=youtu.be
QA Contact: mihai.ninu
I don't know if there's really a better way for us to do this without supporting re-ordering of search engines. I'm tempted to say this should be a WONTFIX.
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.