Closed Bug 1917850 Opened 1 year ago Closed 1 year ago

SearchEngineSelector.fetchEngineConfiguration could be explicit about returning the default engine

Categories

(Firefox :: Search, task)

task

Tracking

()

RESOLVED FIXED
132 Branch
Tracking Status
firefox132 --- fixed

People

(Reporter: standard8, Assigned: standard8)

References

Details

(Whiteboard: [sng])

Attachments

(1 file)

Currently SearchEngineSelector.fetchEngineConfiguration returns a list of engines, and the application default private engine. It is assumed that the application default normal mode engine is the first item in the list.

Although the order rules say that it will be first, I think it is better to be explicit and it saves having to have that knowledge elsewhere in the code.

Whilst we're here, we can also raise explicit errors if there's no default engine found, or if there's no engines at all. This will help us be more explicit about failure situations and actually manages to find some issues in tests.

Also makes fetchEngineConfiguration log or throw errors if it can't find a default engine / all engines.

Summary: SearchEngineSelector.fetchEngineConfiguration chould be explicit about returning the default engine → SearchEngineSelector.fetchEngineConfiguration could be explicit about returning the default engine
Pushed by mbanner@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/533955f713e4 SearchEngineSelector.fetchEngineConfiguration chould be explicit about returning the default engine. r=mcheang
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: