Closed Bug 1026031 Opened 5 years ago Closed 5 years ago

[User Story] Unify settings for Rocketbar and Browser

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect)

x86
macOS
defect
Not set

Tracking

(feature-b2g:2.1, tracking-b2g:backlog)

RESOLVED FIXED
2.1 S3 (29aug)
feature-b2g 2.1
tracking-b2g backlog

People

(Reporter: pdol, Unassigned)

References

Details

(Keywords: feature, Whiteboard: [ucid:System210], [ft:systemsfe])

User Story

As a user, I only want one setting for the search engine used for the Rocketbar (and the Browser) so that I am not confused by having different experiences for each.

Acceptance Criteria:
1. Accessing Search Settings, per UX spec, displays only one setting to choose the search engine.
2. Changing the search engine takes effect for all search entry points (Rocketbar on homescreen, top of screen and launching the Browser via the icon)
No description provided.
User Story: (updated)
Can we close this now as there probably isn't actually anything to do?
Flags: needinfo?(pdolanjski)
Francis, does the latest implementation match your spec for unifying the Settings?
If so, yes, we can close it.
Flags: needinfo?(pdolanjski) → needinfo?(fdjabri)
IIRC there's a new spec which has this setting under "Search" instead of "Homescreen". We probably do need a bug tracking that, but not no "unification" of settings is required.
The spec has been updated to reduce the number of levels that the user needs to navigate. As Ben mentioned, the Search settings have been renamed to "Search" and should be separated from any specific Home screen settings, as the Search is now universal and not just part of home screen.
Flags: needinfo?(fdjabri)
Target Milestone: --- → 2.1 S3 (29aug)
Yes, there's a spec to move the settings, but I think we can handle this in the user story in bug 938177, so there's not a lot of reason to keep this around. Let's close it for now to clean things up a bit.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.