Closed Bug 1826473 Opened 11 months ago Closed 9 months ago

[Unified Search] Remove topical search engines from search settings screen


(Fenix :: Search, enhancement, P2)



(firefox111 disabled, firefox112 disabled, firefox113 disabled, firefox114 disabled, firefox115+ verified, firefox116 verified)

116 Branch
Tracking Status
firefox111 --- disabled
firefox112 --- disabled
firefox113 --- disabled
firefox114 --- disabled
firefox115 + verified
firefox116 --- verified


(Reporter: cpeterson, Assigned: mavduevskiy)


(Blocks 3 open bugs)


(Whiteboard: [fxdroid] [unified-search-mvp])


(5 files)

Bug 1804594 differentiated between general search engines (like Google) and topical search engines (like Amazon). We

As part of the unified search work, a change was made to not allow topical, pre-installed search engines be selected as a default. This results in some of the search engines being greyed out while others are able to be selected. This is confusing because it isn’t clear why those search engines appear disabled nor is there a way to have them become enabled.

The new UX will be designed in

Summary: [Unified Search] Remove topical search engines from → [Unified Search] Remove topical search engines from search settings screen

This bug blocks Unified Search MVP because PM and UX needs to decide whether we ship this current design, a new design, or revert to the old design.

Priority: -- → P1
Attached image screenshot.png

Screenshot of the current design with topical search engines (Amazon, eBay, and Wikipedia) greyed out.

We can't simply remove the topical search engines from this search settings screen because users would then not be able to delete them from the Unified Search menu.

Whiteboard: [fxdroid]
Whiteboard: [fxdroid] → [fxdroid] [unified-search-mvp]
Type: defect → enhancement
Priority: P1 → P2
Assignee: nobody → mavduevskiy
Severity: S3 → N/A

We'd like to fix this bug before we release Unified Search in 115. We don't need to uplift the fix to 114.

Depends on: 1836380
Blocks: 1837113
Blocks: 1837649
Closed: 9 months ago
Flags: qe-verify+
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch

Do we need this on v115?

Flags: needinfo?(mavduevskiy)
Regressions: 1838691

yes, but after QA and UX QA verification.

Flags: needinfo?(mavduevskiy)
Depends on: 1837864

[Tracking Requested - why for this release]:

We'd like to enable the Unified Search UI (bug 1820018) in 115. To do see, we would to uplift this new search engine fix to Beta 115. We'll also want to uplift related bug 1837864 and bug 1838691.

:cpeterson 115.0b9 builds on Thursday, the final beta build of Fx115.
Is there anything preventing an uplift request on this before Thursday? (RE: mentions of verification in Comment 7)

Flags: needinfo?(cpeterson)

I asked QA and the engineer about uplifting before Thursday. If we don't make Thursday's build, we will have to wait until a 115.x dot release or 116.

TBD whether we will still be able to enable the Unified Search UI in 115.0 if we don't have these fixes. Enabling Unified Search might need to wait until that 115.x dot release or 116.

Flags: needinfo?(cpeterson)

Verified as Fixed on Nightly 116.0a1 from 06/21. The Search Settings Screens are displayed as per the Figma design.
We ensured that:

  • General search engines are displayed in the Default search engine sub-menu and an engine can be set as default search engine;
  • Shortcuts for all the available search engines (general/topic-specific and custom engines) are displayed in the Manage search shortcuts sub-menu and can be selected/un-selected;
  • The selected shortcuts in the Manage search shortcuts sub-menu are displayed accordingly in the vertical search menu;
  • Custom search engines can be added from both sub-menus;

Devices used for testing:

  • Samsung Galaxy A53 5G (Android 13)
  • Google Pixel 4 (Android 13)
  • Samsung Galaxy Tab S3 (Android 9)
  • Lenovo Yoga Tab 11 (Android 11)
Flags: qe-verify+

Comment on attachment 9336560 [details] [review]
[mozilla-mobile/firefox-android] Bug 1826473 – add new search engine settings screens (#2274)

Beta/Release Uplift Approval Request

  • User impact if declined: Releasing 115 without it will result in confusing UX experience with search settings. The bug is part of the Unified search project, and UX team raised the issue of redoing search screens as a blocker for shipping the feature. Now, I am not sure if projects are on the same page about it being a blocker, but it definitely makes the user experience much better.
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: Bug 1838691, Bug 1837864
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): It's been in nightly for 9 days, is mostly UI changes and QA has verified it
  • String changes made/needed:
  • Is Android affected?: Yes
Attachment #9336560 - Flags: approval-mozilla-beta?
Comment on attachment 9336560 [details] [review]
[mozilla-mobile/firefox-android] Bug 1826473 – add new search engine settings screens (#2274)

Moving the uplift request to the PR targeting the release branch
Attachment #9336560 - Flags: approval-mozilla-beta?
Attachment #9340367 - Flags: approval-mozilla-beta?
Comment on attachment 9340367 [details] [review]
[mozilla-mobile/firefox-android] Bug 1826473 – add new search engine settings screens (backport #2274) (#2569)

Approved for Fenix 115.0b9.
Attachment #9340367 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

Authored by[bot]
[releases_v115] Bug 1826473 – add new search engine settings screens (backport #2274) (#2569)

Flags: qe-verify+

Verified as Fixed on Beta 115.0b9 as well.
Devices used for testing:

  • Huawei Mate 20 Lite(Android 10)
  • Lenovo Tab P11 Plus (Android 12)
  • Samsung Galaxy Note 8 (Android 9)
  • Oppo Find X5 (Android 13)
  • Huawei MediaPad M2 (Android 5.1.1)
Flags: qe-verify+
Depends on: 1841799
You need to log in before you can comment on or make changes to this bug.