chrome_settings_overrides.search_provider doesn't show confirmation dialogue nor change the default search provider
Categories
(WebExtensions :: General, defect)
Tracking
(Not tracked)
People
(Reporter: mivasi, Unassigned)
Details
Attachments
(1 file)
|
(deleted),
image/png
|
Details |
confirmation.png
We have an addon on AMO that is supposed to change the default search provider. However, in Firefox 111.0.1 (and 112.0b9) on macOS 13.3 (Apple Silicon), when I install the addon from AMO, nothing happens and the default search provider stays intact. Only when I disable and re-enable the addon on about:addons, a confirmation dialogue appears (see confirmation.png).
|
||
Comment 1•2 years ago
|
||
The severity field is not set for this bug.
:willdurand, could you have a look please?
For more information, please visit auto_nag documentation.
|
||
Comment 2•1 years ago
|
||
Hi Michal,
is this reproducible also in a new vanilla profile or only on an existing profile?
(this detail may be useful to us to more easily pin-point what is preventing the default search provider prompt from being shown).
|
|
||
Comment 3•1 years ago
|
||
Hi Alex,
would you mind to try to reproduce this and if it does reproduce to run a bisect using mozregression?
|
||
Comment 4•1 years ago
|
||
Hey Luca,
I could not reproduce the issue on either of the latest Nightly (115.0a1/20230508214159), Beta (114.0b1/20230508175934) and Release (112.0.2/20230424110519) under either Windows 10 x64 and macOS 11.3.1 – I do not have a 13.3 Mac available unfortunately, but I’ll try to get my hands on one asap and repeat the tests.
I’ve also tested Beta 112.0b9 (112.0b9/20230330182947) and Release 111.0.1 (111.0.1/20230321111920), on both mentioned platforms, with the same results as above i.e. I did not reproduce the issue.
Overall, on my end, the confirmation dialogue appears as soon as the extension is installed, the Search Engine is set to the one provided by the extension without issues and also, the Search Engine provided by the extension persists as the set Search Engine after browser restart.
|
Reporter | |
Comment 5•1 years ago
|
||
Hi,
I just tried to reproduce this again to find out whether it only happens on my existing profile or in a new one, too. Unfortunately, I can't really reproduce it anymore both on 111.0.1 and 113.0b9. Can confirm it behaves the same as Alex described. I hope I won't encounter the behaviour I initially described again, but if I will, I'll try to collect more information before it stops happening again.
|
||
Updated•1 years ago
|
Description
•