Currently, the modern configuration is based entirely off list.json. At some stage, we should compare the differences when ABSearch has been applied to list.json, and check if there's anything we should address before we ship the modern config.

For example, with the modern config eBay is currently available to most en-US locales, however, ABSearch turns it off for RO and others.

Depends on D57682

Some more notes here:

• I downloaded the ABSearch data from the live server for each locale/region combination that FF currently supports.
• I then did a xpcshell-test that used some of the current searchconfig test functions to load and reload the engines for different locale/regions using the engine selector.
• This then compared the identifiers of the engines with the list from ABSearch.
• Generally, most things matched:
  • be locale has some differences, due to ABSearch having to support older engines which we don't now.
  • uk locale has some differences, but matches the current list.json which is the best thing to do.
  • zh-TW has the extra readmoo extension.
  • en-US has some differences in the shipped eBay domain (.com instead of the region specific one) - especially on some of the overrides. The patch here fixes those.

Generally though, we're good with matching, so once these have landed, we should be good now.

https://hg.mozilla.org/mozilla-central/rev/f3b42c0737c7