Issue metadata
Sign in to add a comment
|
Omnibox - Suggest Sites with Saved Passwords |
||||||||||||||||||||
Issue description(even if those sites haven't been visited) ainslie@ suggests: >>> I'm trying to get organized about ... and wanted to scheduled .... I normally do it online via ... but I haven't used it in the past 6 months ... so it's not in my recent Chrome history and the omnibox doesn't show suggestions for it. Today I had to find it via the SRP. And I was surprised then that Chrome remembered my password and autofilled it. Could we try making password-origins an omnibox provider? >>>
,
May 16 2017
Sounds like an interesting project idea.
,
Jun 8 2017
,
Jun 27 2017
I'm skeptical this will provide meaningful value. Punting to re-evaluate it next year.
,
Jun 28 2017
Can you add a bit more detail on why you don't think it will add value? Perhaps the sentiment in the description is more about how to make the omnibox remember things I know I've typed/visited before (beyond N months, or however long nav suggest remembers things for). Have we evaluated the usefulness of retaining navsuggest for a longer time?
,
Jun 28 2017
> Can you add a bit more detail on why you don't think it will add value? I'm just skeptical that it's common for users to want to visit a site for which they have a password that they haven't visited in at least three months. I'm also concerned that, even if that's common enough to suggest, that the user will have other passwords from ancient sites, last visited months or years ago, that will then get suggested inappropriately. > Have we evaluated the usefulness of retaining navsuggest for a longer time? No, we have not. There is a request to length in general the history expiration time (bug 692215).
,
Jul 1 2017
Re-adding Hotlist-Polish, which is used by password manager triaging for user-facing changes.
,
Jul 19 2017
,
Jan 9 2018
The NextAction date has arrived: 2018-01-09
,
Jan 10 2018
,
Jan 8
The NextAction date has arrived: 2019-01-08
,
Jan 11
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 11
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ainslie@chromium.org
, May 1 2017