Drew Willcoxon c1f323bbe7 Bug 1541929 - Don't autofill the first result in some cases. r=mak ... We need to handle autofilling the first result separately from autofilling results in general (which happens in UrlbarInput.setValueFromResult), so add a new UrlbarInput.autofillFirstResult method. The controller calls it instead of setValueFromResult. I ported the logic from nsAutoCompleteController, as described in the bug. Other changes are related to the new test for this. As part of this work, I was interested in learning how awesomebar handles browser_autoFill_typed.js, so I added it to the legacy tests, with a small tweak in the test for awesomebar. Differential Revision: https://phabricator.services.mozilla.com/D26852 --HG-- extra : moz-landing-system : lando		2019-04-15 13:15:30 +00:00
..
browser.ini	Bug 1531590, 1531598, 1534811, 1336075, 1531571, 1531572, 1531572, 1531574, 1534855, 1534857, 1535082 - skip tests in mochitest-dev-tools and mochitest-browser-chrome suites for windows10-aarch64 r=jmaher	2019-03-13 19:47:25 +00:00
browser_test_doc_creation.js	…
browser_test_urlbar.js	Bug 1541929 - Don't autofill the first result in some cases. r=mak	2019-04-15 13:15:30 +00:00
head.js	…