Omnibox auto suggestions function
Reported by
rl...@njit.edu,
Mar 18 2017
|
||||||
Issue descriptionChrome Version : All versions URLs (if applicable) : one of many on this subject: https://productforums.google.com/forum/#!topic/chrome/5dE8PIr40NQ Other browsers tested: This is specific to Chrome. What steps will reproduce the problem? (1) Book mark a page. (2) Type "www." without quotes into the url bar. (3) Auto suggestions for the websites you have in your bookmarks will appear What is the expected result? Nothing to be suggested. What happens instead? Websites appear underneath for possible suggestions. Please provide any additional information below. Attach a screenshot if possible.
,
Mar 20 2017
,
Mar 20 2017
Thanks for the report. pkasting@: I feel like this comes up periodically, that users want a way to disable omnibox suggestions entirely (e.g., suggestions from history and from bookmarks, which always appear, even in incognito windows). We have a bug on file ( bug 91378 ) for the discussion and conclusion about disabling inline autocompletion. But I'm not sure if we have a common bug to refer to this entirely-disable request. Know of it?
,
Mar 20 2017
I don't think we have a separate bug for disabling suggestions that isn't "disable inline autocompletion". I'd like to better understand what problem users who ask for this are trying to address. Are suggestions distracting? Are they not generally relevant enough to be useful, so why bother having them? Are they covering useful page content in particular cases? Are they revealing private data? Something else? It's hard to know how to solve/dupe this without understanding what problem the proposed solution is aiming at.
,
Mar 20 2017
rl265@njit.edu: Can you provide details on why you don't want any suggestions to appear? Nothing in that thread you link to provides details about the "why".
,
Mar 21 2017
My personal reasons are that its a bit revealing and not conducive to privacy. I do not like that anyone can go on my computer and type in "www." And see that all my bookmarks. I don't think it is necessary to have and no other web browser that I've seen has this issue. It isn't convenient to open google in incognito just to avoid this issue. It would be better to have an option to disable this feature. Example: Let's say I have a personal illness that I do not want to advertise to others and bookmark links of my illness to refer back to. Having those links reveal something personal would obviously not be wanted. I hope this is made more clear.
,
Mar 21 2017
Thank you for providing more feedback. Adding requester "mpearson@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 21 2017
I'm confused. How is it different for those people to simply open your bookmark list? That list is not protected or hidden in any way and it takes fewer keystrokes to open it than to type "www.".
,
Mar 21 2017
I believe I've read all the suggested fixes for this issue, but none of them resolve the actual issue. It seems that this is an ongoing issue with no fix, hence my email to suggest that there be one.
,
Mar 21 2017
That doesn't answer my question.
,
Mar 21 2017
Regardless of why, is personal preference not enough? I'd be happy to inform you on my personal reasons why I'd like this disabled, however, I don't see how it would be anymore difficult to disable this feature without knowing the "why". First off, the popups are generally bothersome and annoying visually. Nothing more to it than that for this point. Second, its a bit revealing and not conducive to privacy. I do not like that anyone can go on my computer and type in "www." And see that all my bookmarks I have. I don't think it is necessary to have and no other web browser that I've seen has this issue. It even happens in incognito mode. Example: Let's say I have a personal illness that I do not want to advertise to others and bookmark links of my illness to refer back to. Having those links reveal something personal would obviously not be wanted. I hope this is made more clear.
,
Mar 21 2017
Unfortunately it's not more clear. You're restating what you stated before. Basically, you're concerned about people finding out personal information via bookmarked URLs via typing in the address bar and having those bookmarks appear. But it's even easier for such people to simply look at your bookmarks. We wouldn't provide any privacy win for you by disabling this. So disabling this doesn't seem to solve the problem. The reason we ask the "why" is that we're interested in really solving people's problems. For example, if you have private data that you don't want available to others, it seems like proper features to discuss might be things like password-protected profiles, or whether Chrome is even capable of providing this, rather than providing an option which won't keep your data private.
,
Mar 21 2017
I think you're missing the point. It is personal preference that the bookmarks are disabled from autosuggestion. What is the point of disabling autosuggestion for your search history, yet not including an option for bookmarks? Regardless of your answer, this is obviously an issue for more than just myself. People want this feature, why go around it?
,
Mar 21 2017
It seems like you are looking for bigger problems to solve rather than taking care of the small ones. Regardless of whether you are satisfied with my reasons does not solve the issue.
,
Mar 21 2017
Preferences don't happen in a vacuum; someone wants something in order to solve a problem. We want to solve those problems too. We can't simply implement every request because people ask for it, because we have billions of users and get tens of thousands of requests, and those requests conflict with each other and would make the product more complicated. So we have to figure out what our users' problems are and then try to design solutions that will address them. We don't allow disabling search history suggestions either; for example, the omnibox will still make local search history suggestions, and there's no current way to disable that. We _do_ allow disabling the feature that uses server-provided data for suggestions, because that requires sending some of your keystrokes across the network to a remote server, and we'd like users to avoid having to ever send that data. For this specific feature, one reason not to do it is that it's not clear what's desired yet. For example, you spoke of bookmarks, but disabling bookmark-based suggestions is very different than disabling all suggestions. Someone might legitimately want to not have bookmark suggestions, but still have other suggestions; someone else might not want non-URL suggestions; someone else might want no suggestions at all. We've been asked for specific key modifiers to control which suggestions appear, special operators to type in the address bar to control suggestion matching, and every possible combination of options. These represent well-intentioned desires on the part of lots of people, but there's no reasonable way to implement them all, and even implementing some will result in engineering effort, code complexity, testing burden, string translation, binary size increase, UI cognitive complexity increase, etc. All these are costs we have to decide carefully about how to pay, and knowing we're actually solving users' real problems is the way we measure that those costs are worth it.
,
Mar 21 2017
Seems like a big issue to many people, but that's good to know that this problem will not be addressed rather than assuming there will be something done. Take care.
,
Mar 21 2017
We're perfectly willing to address this, if it can be stated as a problem we can solve, rather than a solution that we have to implement (or else we're seen as not solving the problem). So far, the problems stated are: * Popups are bothersome -- can you say more about this? Bothersome in what way? How do they interfere with what you're trying to do? * Possible reveal of private information -- seems like a real problem that removing some/all omnibox suggestions doesn't solve
,
Jun 26 2017
Closing because adding a configuration for this isn't a common enough request to spend engineering time to implement and support. Sorry reporter, I understand who want this, but we cannot implement everything that everyone wants... |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by rl...@njit.edu
, Mar 18 2017