defaultEngineId does not support an _isAppProvided: false search engine
Categories
(Firefox :: Search, defect)
Tracking
()
People
(Reporter: crfud0ss, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:108.0) Gecko/20100101 Firefox/108.0
Steps to reproduce:
Firefox used to allow configuring search engines via search.json.mozlz4, however on version 108.0b1 this no longer seems to work for non-builtin search engines (ones with _isAppProvided: false).
This seems related to the changeset 714274 (aac389dbe3cb61fb13d7a38332f941e594361e69)
Steps to reproduce:
- Create a new Firefox profile
- Add a new custom search engine to the profile (e.g. add the following to engines array:)
{
"id":"582076c8-4739-4996-992c-41df0982d240",
"_name":"HackerNews",
"_isAppProvided":false,
"_urls":[{"template":"https://hn.algolia.com/?q={searchTerms}"}],
"_metaData":{"alias":"!hn","order":4}
}
- Set the default search engine to the custom search engine in search settings page
- Copy search.json.mozlz4 to a new Firefox profile
Actual results:
Observe that default search engine reverts to Google.
Expected results:
Expected default search engine to remain set to HackerNews.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Search' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•3 years ago
|
||
(In reply to crfud0ss from comment #0)
- Copy search.json.mozlz4 to a new Firefox profile
Actual results:
Observe that default search engine reverts to Google.
Expected results:
Expected default search engine to remain set to HackerNews.
The default engine protection includes the profile directory, so copying search.json.mozlz4 across to a different profile would have reset the default engine to the application default.
I've just verified that this is what happens on 106.0.5, so I believe the behaviour here is as expected/designed.
This is a bit sad because it means I can no longer configure the default search engine through dotfiles and must resort to using a UI. Is there really no way to configure this using a configuration file?
Description
•