-
Notifications
You must be signed in to change notification settings - Fork 506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
firefox suggest #1257
Comments
Flipping this to false hides the "Firefox Suggest" label in the address bar in FF92. https://www.ghacks.net/2021/09/09/how-to-disable-firefox-suggest/ |
right, and it requires a reset to take effect. as a FYI, you can also hide it via CSS .urlbarView-row[label="Firefox Suggest"]::before{ display: none !important; }
.urlbarView-row[label="Firefox Suggest"]{ margin-top: 0 !important; } |
So is this the master switch or not? Anyone? Feel free to look at the source, otherwise I'll see if I can get around to it in the next four weeks and then put out a v92 - TIA edit: what I had as a working draft, last edited 10 days ago
/* xxxx: disable contextual suggestions [FF92+]
* [SETTING] Privacy & Security>Address Bar>Contextual Suggestions
* [1] https://support.mozilla.org/en-US/kb/navigate-web-faster-firefox-suggest ***/
user_pref("browser.urlbar.suggest.quicksuggest", false);
// user_pref("browser.urlbar.suggest.quicksuggest.sponsored", false);
user_pref("browser.urlbar.quicksuggest.enabled", true); |
On the two checkboxes
This is enough AFAICT. This is the top checkbox, the sponsored child checkbox is shown as unchecked at runtime. The value in about config is simply it's state should you flip the parent on.
We could add the sponsored one as a pair The sponsored checkbox one remembers it's state, but if the top one is unchecked (either manually or via user.js on startup), when you look at settings in runtime, both are unchecked |
AFAICT ....
I don't really care about the last point, because we're turning off the two types at a lower level, which seems simplest and reliable, and AFAIK nothing can ever be sent until you are enrolled and opt-in - sorry, can't be fked trying to find the comment which quoted some doc/code |
https://bugzilla.mozilla.org/show_bug.cgi?id=1729776#c3 explains what they flip/do |
I tested this on 94beta again and I don't think I need a restart to kill the label, at least on en-US builds.
The pics only showed segregation between live suggestions from search engines and (presumably) contextual suggestions from Firefox. What they didn't show is that other "suggestions" from Firefox (e.g. your own bookmarks, history, opened tabs, synced tabs etc...) will also be shown under the same label, so mozilla's product team were effectively rebranding their browser urlbar dropdown. And this user.js disables live search suggestions by default (in 0804?) anyway so IMO those pics do not tell the entire story. |
The first pic clearly shows a I don't really care about if a restart is required or not, because the pref is useless for our purposes. If you want contextual (which is from a local list), then at least let that shit be labeled :) |
sums it up nicely for now: https://old.reddit.com/r/firefox/comments/q5ipc5/firefox_suggest_gets_me_confused/hg5vk9n/ Looking at https://bugzilla.mozilla.org/show_bug.cgi?id=1729776#c3 .. it's not clear if users will get an onboarding dialog - I DIDN'T (I am en-US and region US), emphasis mine - but that's because no-one has been given "online" except in testing - and the patch and blogs explicitly say onboarding is for online, so that clears that up, phew
This is my issue, we can't set scenario (see OP) and I'm not 100% certain the user.js changes stick for the first run after an update. How often does browserglue run? Surely they have to respect users decisions (in my FF93 which is en-US and US region, they were both enabled after I updated, but once added to user.js they stick) https://hg.mozilla.org/mozilla-central/rev/04a89fcd7400
We're opted out of experiments, so my only concern would be default update changes and runtime
Anyone have anything else to offer? I don't think we can set the scenario, and setting |
|
new UI from 94.0.2:
|
is this from https://bugzilla.mozilla.org/show_bug.cgi?id=1735976 ? |
yup. unless you want to block suggestions from firefox or enforce the dataCollection pref the current setup is good. also, not very relevant for arkenfox but as a follow up to my previous comment, neither of the above prefs could prevent opt-in my later tests. I evened tried with |
I'm happy with the prefs we set so far. I've monitored my test FFs to see what happens, and my main FF - e.g. i can't find it now, but I noticed one of my profiles has a bunch of files for categories of suggestions. So far nothing like that has been downloaded in my main arkenfoxed FF, and I haven't been prompted to opt in I noticed that bugzilla a few days ago, and was going to address it in FF96 diffs, but happy to reopen this as a reminder |
https://bugzilla.mozilla.org/show_bug.cgi?id=1735976 was added to beta, and will be handled in 94-95 diffs |
For the record, these four prefs are all |
Lines 310 to 315 in 33a84b6
There seems to be something wrong with the description here, it doesn't cause the |
The "work" refers to "live search" - and AFAICT this is real time search results from the search engine - that's what "LIVE" search means. I just tested. Both prefs off .. silence ... one pref on .. silence ... both prefs on live results per keystroke |
I mean:
Please forgive my nitpicking. |
so using some common sense ... we are setting at least one of the prefs to false .. so by your logic we are deliberately breaking the location bar so it can't be used |
moving to a separate topic for v92
fxbrit said
FIY: quicksuggest aka "Firefox Suggests"
browser.urlbar.quicksuggest.enabled
controls wether the UI is shown or not (screenshot to follow). I think it works as a master switch for the whole feature but I haven't done any in depth testing.browser.urlbar.quicksuggest.scenario
which can be set toonline
,offline
orhistory
, and which enables the quicksuggest experiment (I call it experiment cause that's what firefox calls it in its source code). even if I setbrowser.urlbar.quicksuggest.enabled
to false with a .cfg file (bothdefaultPref
andpref
) that value would be changed to true based on the scenario.pref
(otherwise overwrote, but it doesn't matter for user.js files and I was just being precise). sobrowser.urlbar.quicksuggest.scenario
=""
, which guarantees thatbrowser.urlbar.quicksuggest.enabled
=false
.browser.urlbar.suggest.quicksuggest
andbrowser.urlbar.suggest.quicksuggest.sponsored
control the checkboxes in the UI (again screenshot to follow)browser.urlbar.groupLabels.enabled
didn't do anything for me, although I've read online a few times that it is used to control firefox suggests. no idea.finally the screenshot (Settings > Privacy & Security > Address Bar) :
when the experiment is enabled "Address Bar" name changes to "Address Bar - Firefox Suggests".
The text was updated successfully, but these errors were encountered: