1513532 - Wishlist Group Policy Settings: browser.urlbar.suggest.searches and browser.urlbar.searchSuggestionsChoice

Status: VERIFIED FIXED

(Firefox :: Enterprise Policies, defect, P2)

Description

[Mark Heitbrink]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:63.0) Gecko/20100101 Firefox/63.0

Steps to reproduce:

I would like to control browser.urlbar.searchSuggestionsChoice and browser.urlbar.suggest.searches by Group Policy (Registry DWord).

Suggestions from any Search Engine should be disabled because of GDPR, at least it should be controlled centrally with Group Policy.



Expected results:

Open GPEditor, import ADMx, set and configure value.

Comment 1

[Mark Heitbrink]

Sorry, P3 is probably a wrong level of priority.

Compare this to Manage connections from Windows operating system components to Microsoft services (https://docs.microsoft.com/en-us/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services)

Site guessing by the searchengine produces data, which I probably want to keep, just because of Privacy reasons!

I can disable this possibility in IE, Edge and Chrome by Group Policy. Firefox is not enterprise ready, if it can not be controlled like any other Browser. "No Control on FF" is an argument PRO Chrome.

To me, full functional Group Policy capability is P1. Otherwise FF will stay at Home and Endusers.

Just my 2 cents.
Mark

Comment 2

[:Felipe Gomes (needinfo for replies!)]

Ok, agreed. I'll bump it to P2 (P1 is reserved for bugs on existing policies, regressions or things already in progress)

Comment 3

[Mike Kaply [:mkaply]]

browser.urlbar.searchSuggestionsChoice is unused except for migration. I'm going to use this bug to add policies for all of the address bar search policies

browser.urlbar.suggest.searches (Search suggestions)
browser.urlbar.suggest.openpage (Open Tabs)
browser.urlbar.suggest.history (Browser History)
browser.urlbar.suggest.bookmark (Bookmarks)

For my reference, name of policy on Chrome is:

SearchSuggestEnabled

Open question is should all four prefs be controlled by the one policy? Are all of these items considered "SearchSuggest" or does search suggest specifically refer to getting search keyword suggestions?

Comment 4

[Mike Kaply [:mkaply]]

To answer my own question, I think it should turn off everything (especially history). In an enterprise scenario on a shared computer, you don't want random results coming up.

Comment 5

[Mark Heitbrink]

From the idea of data privacy, suggestion from your local /cahced history and bookmaks are ok. Thats how Chrome, IE and Edge handle it. For me it´s the Search suggestion by search engine, the others are optional. It could be one Policy containing 4 parts with a checkboy and the damin can decide.

Comment 6

[Mike Kaply [:mkaply]]

Attachment: Bug 1513532 - Add policies for search suggestions.

Comment 7

[Mike Kaply [:mkaply]]

With our new pref policies, this is much easier.

I've added the main policy - SearchSuggestEnabled - to emulate Chrome.

I've added the additional items as preferences policies if people want them.

Comment 8

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/2e24668fe392
Add policies for search suggestions. r=Felipe,flod

Comment 9

[Daniel Varga [:dvarga]]

https://hg.mozilla.org/mozilla-central/rev/2e24668fe392

Comment 10

[Emil Ghitta, QA [:emilghitta]]

This issue is verified fixed using Firefox 68.0b5 (BuildId:20190527103257) on Windows 10 64bit, macOS 10.14 and Ubuntu 18.04 64bit.