New issue
Advanced search Search tips
Starred by 10 users

Issue metadata

Status: Duplicate
Merged: issue 68177
Owner: ----
Closed: Dec 2010
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature

  • Only users with Commit permission may comment.

Sign in to add a comment

Issue 65588: Provide way to disable automatic addition of search engines

Reported by, Dec 6 2010 Project Member

Issue description

Chrome Version       : 8.0.552.215 (Official Build 67652)

Chrome automatically collects search engines as it walks the Internet. Over time, this results in a long list of search engines which may not be desirable and bothering to a user. For example, if a search engine is added with a certain keyword, searching by that very same word in the address bar causes a "conflict", i.e., the search engine will be preferred over a regular Google search.

What I have in a mind as a possible solution to this issue is a similar mechanism as Chrome's translation feature: When the first search engine is found and to be added, fade in a small bar at the top of the browser notifying the user of the subsequent addition, including options to change the default behavior (i.e., disabling the addition of further search engines from now on). This should be accompanied by a settings page/tab where the user may change his or her mind afterwards. For example, the user may wish to re-enable the search engine collection feature permanently or temporarily in the future.

Comment 1 by, Dec 6 2010

Labels: -Type-Bug -Area-Undefined Type-Feature Area-UI Feature-Omnibox

Comment 2 by, Dec 6 2010

Status: WontFix

Comment 3 by, Dec 6 2010

Could you explain why this is a WontFix? I think a gave a good first reason why making search engine additions configurable would be worthwhile.

Besides, I do not seem to be the only one who'd find such a change likeable:

Comment 4 by, Dec 6 2010

We eschew configuration UI and user prompts.  This doesn't rise to the exceptional level that justifies such things.

Comment 5 by, Dec 6 2010

Although I somewhat fail to see how the proposal I described does not fit into Chrome's way of dealing with interactivity-related issues by means of fading in a temporary bar (the browser keeps asking me about various things that way, e.g., password remembering, extension right changes, etc.), I am sure there are other, more easily accepted approaches.

One much less intrusive kind I can think of is provide a single checkbox in search engines' "manage" window that, when ticked, prevents the addition of further search engines. Its label could be something like "stop collecting search engines". It should be quite simple to implement and not interfere with the main browser UI while allowing users that prefer to manage search engines themselves to do so.

Comment 6 by, Apr 27 2011

I agree, there should be a way to disable collection, or maybe even better: having three lists: "Standard search engines", "my search engines" and "collected search engines", where you can make a "collected search engine" a "my search engine".

This would nicely address the issue of "which search engines did I actually want to keep last time I checked? And which search engines are completely new?"

Comment 7 by, Jun 25 2011

pkasting: what about the privacy implications of this?  how many people know that somebody can come up to their Chrome session, right-click on their Omnibox, and get a good idea of the types of site that the user visits?

Comment 8 by, Jun 26 2011

Why would we worry about that when said person can walk up and hit ctrl-H to see the user's entire history in detail?  Or ctrl-T for a page with the top 8 most visited sites?

This is way down on the list of theoretical threats.

Comment 9 Deleted

Comment 10 by, Jun 27 2011

Got a comment 9 in my email but I don't see it here, I don't know why.

Anyway it notes that perhaps these should be clearable from the Clear Browsing Data dialog.  Similar arguments could perhaps be made about the content settings.  I filed bug 87685 to discuss that.

Comment 11 by, Oct 12 2012

Project Member
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.

Comment 12 by, Dec 4 2012

Mergedinto: 68177
Status: Duplicate

Comment 13 by, Mar 11 2013

Project Member
Labels: -Area-UI -Feature-Omnibox Cr-UI-Browser-Omnibox Cr-UI

Sign in to add a comment