Closed Bug 1870652 Opened 1 year ago Closed 1 year ago

In search-config-v2 change the defaultEngines records to have a single field for default/defaultPrivate matches

Categories

(Firefox :: Search, task, P2)

task

Tracking

()

RESOLVED FIXED
123 Branch
Tracking Status
firefox123 --- fixed

People

(Reporter: standard8, Assigned: standard8)

References

Details

(Whiteboard: [sng])

Attachments

(2 files)

On the engine orders record in search-config-v2, we've implemented an exact match or starts with match mechanism. This allows us to specify an engine identifier as wikipedia for an exact match, or wikipedia* for a starts with match.

We want to bring that across to the default engines record so that we can drop the default vs defaultStartsWith splits (normal + private), and have more consistency within the configuration.

Drop the requirement for disallowing additional properties in the order section as remote settings as its own properties, and this wasn't meant to be included.

We do check additional properties in xpcshell-tests, but need to allow for additional properties at runtime in case configurations are extended.

Depends on D196737

Pushed by mbanner@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/4bda3f55164a In search-config-v2 change the defaultEngines records to have a single field for default/defaultPrivate matches. r=mcheang https://hg.mozilla.org/integration/autoland/rev/85d549eafb17 Remove unnecessary additionalProperties requirement in search-config-v2-schema. r=mcheang
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 123 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: