Closed Bug 1600715 Opened 6 years ago Closed 6 years ago

searchUrlGetParams in the modern configuration does not specify the parameter order

Categories

(Firefox :: Search, task, P1)

task
Points:
3

Tracking

()

RESOLVED FIXED
Firefox 73
Iteration:
73.1 - Dec 2 - Dec 15
Tracking Status
firefox73 --- fixed

People

(Reporter: standard8, Assigned: standard8)

References

Details

Attachments

(2 files)

I've just noticed that with the modern configuration, searchUrlGetParams is an object with indeterminate order of the keys.

This is effectively a regression with the modern configuration - bug 1484232 intentionally changed the order of our parameters to better serve people using Google.

We need to be able to specify the order, like we can do with the current legacy configuration and WebExtensions.

Realistically, this probably means switching searchUrlGetParams and related items to be arrays of objects.

Ideally we should do this before landing bug 1542269, as it'll make it slightly simpler overall.

Note: I picked this up as some of our tests currently break with modern configuration turned on due to the wrong order of keys.

We might as well do this for now to keep the tests passing when modern config is turned on. It doesn't actually matter what order these particular parameers are listed in.

Depends on D55640

Pushed by mbanner@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/67a38267ec0b Change the searchUrlParams in the modern config to be an ordered array of objects. r=mikedeboer https://hg.mozilla.org/integration/autoland/rev/f25b6b1800eb Match the order of the extraParams for search engines to the existing lists. r=mikedeboer
Blocks: 1601633
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 73
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: