1895934 - Improve handling of search term parameter names

Status: NEW

(Firefox :: Search, task, P3)

Description

[Mark Banner (:standard8)]

With the new search configuration, we now have a dedicated searchTermParamName. For application provided engines, we should be able to use those details directly, rather than going through the conversion to a URL and look for {searchTerms} process.

It might be that we extend EngineURLs with a specific option for the search term, rather than having AppProvidedSearchEngine add a "normal" parameter.

Some exploration might be needed for the best way of doing this. Ideally, we'd potentially only process once the search term parameter name for other engine types as well.

Whilst here, or maybe in a follow-up, we should also update SearchEngine.searchTermFromResult to get the search term parameter name directly, rather than going through getURLParsingInfo(). This would be more efficient in avoiding unnecessary conversions of the URL template to a nsIURI.