Closed Bug 422151 Opened 13 years ago Closed 12 years ago
In location bar autocomplete ignore results with a particular tag (like "private") to help users protect their privacy
Several users have commented that they like the new location bar autocomplete, but that they are concerned that it is showing bookmarks for certain sites that that could cause embarrassment if displayed. Users have also noticed that the large and easy to read font we are using for page or bookmark titles makes it easier for other people to see this information as well. What if we didn't show any results in the user's bookmarks that contained the tag "private." Even after we implemented private browsing mode, this feature would be useful for users that want to bookmark a page, but not have firefox repeat that bookmark back to them.
Not for Fx3, but a good target for the future.
Summary: Ignore results with a particular tag to help users protect their privacy? → In location bar autocomplete ignore results with a particular tag (like "private") to help users protect their privacy
Apparently bug 395161 makes this easier.
It would be important to implement this feature for the launch date of Firefox 3. Many people I know will not install this version by this "problem of privacy."
What would be the UI for this feature? / How would it be discovered? Also, what is the migration path? Can people just tag a whole folder of bookmarks after they upgrade or do they have to do it one by one?
>What would be the UI for this feature? / How would it be discovered? funny you should ask, I just finished the mockup for specifying tags a few minutes ago: http://people.mozilla.com/~faaborg/files/shiretoko/privacy_i2.png >Can people just tag a whole folder of >bookmarks after they upgrade or do they have to do it one by one? We are probably going to add a checkbox to folders under their properties to exclude them from the location bar autocomplete. We should also have support for tagging multiple bookmarks in the Library window.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 450314
You need to log in before you can comment on or make changes to this bug.