Closed Bug 1038775 Opened 10 years ago Closed 10 years ago

Always launch search activity on dashboard

Categories

(Firefox for Android Graveyard :: Search Activity, defect)

All
Android
defect
Not set
normal

Tracking

(firefox34 verified)

VERIFIED FIXED
Firefox 33
Tracking Status
firefox34 --- verified

People

(Reporter: eedens, Assigned: eedens)

References

Details

Attachments

(1 file, 1 obsolete file)

- On launch, don't focus search bar - Clear last search every time the activity is loaded - Always start the activity on the dashboard - Don't show provider suggestions for empty query
Removing query bar items, since bug 1035341 touches that code, and will cause a lot of conflicts. New scope: - On launch, don't focus search bar - Always start the activity on the dashboard
Summary: Launch experience improvements for search activity. → Always launch search activity on dashboard
Attached patch bug-1038775.patch (obsolete) — Splinter Review
Attachment #8456404 - Flags: review?(margaret.leibovic)
Comment on attachment 8456404 [details] [diff] [review] bug-1038775.patch Review of attachment 8456404 [details] [diff] [review]: ----------------------------------------------------------------- ::: mobile/android/search/java/org/mozilla/search/MainActivity.java @@ +27,3 @@ > } > > private State state = State.START; Not directly related to this bug, but is State.START ever used for anything? If not, I think we could just get rid of it. Also, I find the terms "presearch" and "postsearch" a bit confusing. Do we even need states here? I would like to think about ways we can rename the fragments to be more intuitive. Perhaps something like InitialFragment and ResultsFragment? I'm having a tough time coming up with a good name for the first one. Also, SearchFragment could probably be renamed to AutoCompleteFragment, since the whole activity is about searching, so using the term in there can be confusing. Sorry for the digression, I'm just making my way through all this code right now :) @@ +44,5 @@ > + @Override > + protected void onResume() { > + super.onResume(); > + // When the app launches, make sure we're in presearch *always* > + // Bug 1038775. You don't need to include a bug number in a comment if it's the bug you're currently working on (blame can lead us back to this bug). ::: mobile/android/search/java/org/mozilla/search/PostSearchFragment.java @@ -61,5 @@ > > public void startSearch(String query) { > setUrl(Constants.YAHOO_WEB_SEARCH_BASE_URL + Uri.encode(query)); > } > - Did you mean to remove this empty line?
Attachment #8456404 - Flags: review?(margaret.leibovic) → review+
For the naming feedback -- I think you're right. There's a lot that we can do to make the structure more intuitive. I opened bug 1038924 for us to review that once the churn from this week settles. ACK on the bug numbers, and thanks for catching that empty line.
Attachment #8456404 - Attachment is obsolete: true
Attachment #8456457 - Flags: review?(margaret.leibovic)
Attachment #8456457 - Flags: review?(margaret.leibovic) → review+
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 33
Verified as fixed in build 34.0a1 (2014-08-04); Device: Asus Transformer Tab (Android 4.2.1).
Status: RESOLVED → VERIFIED
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: