Closed Bug 1502821 Opened 2 years ago Closed 2 years ago
.urlbar .suggest .bookmark false is no longer respected
47 bytes, text/x-phabricator-request
|Details | Review|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0 Steps to reproduce: Have bookmarked sites, and don't have them in your history. Uncheck Options > Privacy & Security > Address Bar > When using the address bar, suggest: Bookmarks. Or set browser.urlbar.suggest.bookmark false in about:config (Update from FF 62 to FF 63). Actual results: Start typing the bookmarked site in the address bar, and notice that it suggests the bookmarked site, despite the setting not to use bookmarks as a suggestion source. Expected results: Bookmarks should not be used as a suggestion source while this setting is false/uncheked, bookmarked sites should not be revealed and presented when typing in the address bar.
New Firefox version no longer uses moz_hosts, instead it suggests host from moz_origins. With this change, it ignores setting "Suggest from Bookmarks" and autocompletes url. It also seems to ignore or bypass frecency, still suggests at negative values.
It's likely a fallback from bug 1488879 and bug 1493636
This bug is still present in 64.0
Summary: Firefox 63 not honouring browser.urlbar.suggest.bookmark false → Firefox 63,64 not honouring browser.urlbar.suggest.bookmark false
Thanks for the update, but there's really no need to update titles/bugs for each version. This is a P1 issue and we'll hopefully get to it soon.
Summary: Firefox 63,64 not honouring browser.urlbar.suggest.bookmark false → browser.urlbar.suggest.bookmark false is no longer offered
Summary: browser.urlbar.suggest.bookmark false is no longer offered → browser.urlbar.suggest.bookmark false is no longer respected
Iteration: --- → 70.1 - Jul 8 - 21
Points: --- → 3
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/a0d1724c35aa Don't autofill bookmarks when browser.urlbar.suggest.bookmark is false. r=mak
You need to log in before you can comment on or make changes to this bug.