As of bug 1676469, `browser.urlbar.maxHistoricalSearchSuggestions` is treated as a boolean. If it's zero, then we don't show form history; otherwise we do, and the number of form history results is determined by flex. Marco [suggests](https://phabricator.services.mozilla.com/D99281#3394287) that we migrate the pref to a new `browser.urlbar.suggest.searchHistory` pref and also expose it in the prefs UI. This bug can be about the new pref and maybe also the prefs UI change, but we already have bug 1643479 for making larger changes to the UI. If we don't want to block this on that bug, then I would recommend scoping this bug to only the migration and then filing a new bug for the smaller prefs UI addition. For now I'll add bug 1643479 as a see-also.
Bug 1691801 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
As of bug 1676469, `browser.urlbar.maxHistoricalSearchSuggestions` is treated as a boolean. If it's zero, then we don't show form history; otherwise we do, and the number of form history results is determined by flex. Marco [suggests](https://phabricator.services.mozilla.com/D99281#inline-584753) that we migrate the pref to a new `browser.urlbar.suggest.searchHistory` pref and also expose it in the prefs UI. This bug can be about the new pref and maybe also the prefs UI change, but we already have bug 1643479 for making larger changes to the UI. If we don't want to block this on that bug, then I would recommend scoping this bug to only the migration and then filing a new bug for the smaller prefs UI addition. For now I'll add bug 1643479 as a see-also.