App-provided engines should use the engine configuration when they are updated
Categories
(Firefox :: Search, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox80 | --- | fixed |
People
(Reporter: standard8, Assigned: standard8)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
I noticed that the app-provided engines do not get the configuration re-applied when they are updated.
This could cause a period of time when the engine is in use but doesn't have the correct parameters applied (I think it would fix itself on restart).
Once bug 1637744 is done (which will make this easier), we should look at obtaining the current configuration and passing that to the update handling routines.
Assignee | ||
Comment 1•4 years ago
|
||
Taking this as I think I need it for bug 1610293, though we should get it done anyway.
Assignee | ||
Comment 2•4 years ago
|
||
Currently we're converting the configuration url parameters to strings in makeEngineFromConfig via URLSearchParams. We then pass them through URLSearchParams again in _initEngineURLFromMetaData.
Depends on D82525
Assignee | ||
Comment 3•4 years ago
|
||
Depends on D82583
Comment 5•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/49f8a11bbd1a
https://hg.mozilla.org/mozilla-central/rev/974e5d55e4f3
Description
•