"Trash" feature for bookmarks
Categories
(Firefox :: Bookmarks & History, enhancement)
Tracking
()
People
(Reporter: yoasif, Unassigned)
References
Details
(Keywords: parity-opera)
Like the bookmarks feature in Opera Desktop.
This would replace the "delete" feature of bookmarks today.
The following use case should be possible.
- Create bookmark
- Navigate to Library
- Right click on bookmark > select "Move to Trash"
The bookmark should now appear in the "Trash", a special folder within the Bookmarks Library.
User should be able to empty the trash, and right clicking on a bookmark in the trash should allow a user to permanently delete the bookmark.
The "delete" function should also move to trash.
User should also be able to revert the move to trash; this is available in Opera, but good prior art can likely be seen in macOS as well.
Bookmarks moved to trash should not show up as bookmarked in awesomebar queries.
Bookmarks in Trash should be synced.
|
Reporter | |
Updated•6 years ago
|
|
||
Comment 1•6 years ago
|
||
What's the significant benefit for the end user here? We already have undo for the library, plus we keep a couple of weeks of backups of bookmarks, which could be used for recovering.
|
|
Reporter | |
Comment 2•6 years ago
|
||
In my testing undo does work, but I submitted this bug in response to user feedback here: https://www.reddit.com/r/firefox/comments/b044aq/i_have_lost_a_bunch_of_important_bookmarks_dont/ where the user says that the undo feature did not work.
why can't you make a simple trash folder to collect deleted bookmarks instead of the stupid undo function which you could not even make to work right?
I think the significant benefit here is simply that this is a nicer undo than undo -- I think there is a reason that desktop OSes have a recycle bin or trash -- instead of disappearing into the ether and knowing beforehand that an undo is available (Firefox doesn't do a great job in exposing this like a web app might, and newer computer users may not expect an undo to be available), the bookmark is moved to a trash bin that users can periodically empty (or remove manually).
A trash feature also persists across sessions and while this is not a Fennec/Fenix bug, "undo" can be very hard to get to in mobile OSes (if a user misses a snackbar notification, for instance).
|
||
Comment 3•6 years ago
|
||
(In reply to Asif Youssuff from comment #2)
In my testing undo does work, but I submitted this bug in response to user feedback here: https://www.reddit.com/r/firefox/comments/b044aq/i_have_lost_a_bunch_of_important_bookmarks_dont/ where the user says that the undo feature did not work.
It's unclear why it didn't work, maybe he restarted the browser and undo is just for the session. but that user seems to have a lot more problems, I don't see how he doesn't have any backups, when we store backups for more than 15 days...
I think the significant benefit here is simply that this is a nicer undo than undo -- I think there is a reason that desktop OSes have a recycle bin or trash -- instead of disappearing into the ether and knowing beforehand that an undo is available (Firefox doesn't do a great job in exposing this like a web app might, and newer computer users may not expect an undo to be available), the bookmark is moved to a trash bin that users can periodically empty (or remove manually).
A trash feature also persists across sessions and while this is not a Fennec/Fenix bug, "undo" can be very hard to get to in mobile OSes (if a user misses a snackbar notification, for instance).
On mobile bookmarks are not that much used in general, mobile is known for short sessions, managing bookmarks is not such a big thing, thus I don't see mobile implementing that, but never say never.
The Trashcan feature has a few benefits against undo, I don't doubt it, but it also has downsides, that is why we currently don't consider it viable:
- Privacy: most of our users care a lot about data going away when it's removed. We don't consider bookmarks a top tier info for privacy, but still removing something should be a definitive action.
- Cost: implementing a trashcan means bookmarks should be marked as "deleted" but stay there, then everything must filter out those bookmarks and notifications for them, and we know how inefficient is (because we do that for tags and we want to stop it!)
- UI: it obviously would require adding more UI pieces, and we can barely manage what we have already with the resources at hand
Considered we already have workarounds to losing bookmarks in the shape of:
a: undo in the session
b: backups for at least 15 days (usually more)
it looks like the cost of a trashcan feature ends up overwhelming the real benefits.
I'd rather spend time making existing features better, for example UNDO is undiscoverable, if we'd merge it into the global Edit menu then one could just undo from the main browser window... As well as if the library would be redesigned in content, we could make it more visible.
Thus, I'm sorry, but at this time I don't see us adding this feature.
| Comment hidden (metoo) |
|
||
Comment 7•5 years ago
|
||
To argue:
- undo only work when user immediately realises a mistake
- backup is a workaround but only for power user ... I could recover data but it required a lot of manipulations
- I am not convinced that the implementation of a trash table, as a virtual folder like history, is more complicated than undo
(In reply to Mark Banner (:standard8) from comment #1)
What's the significant benefit for the end user here? We already have undo for the library, plus we keep a couple of weeks of backups of bookmarks, which could be used for recovering.
Firefox should be a browser for the majority, not just for people who know how to make a backup of bookmarks.
If this feature will make Firefox gain 0.1% marketshare i say let's do it.
|
|
||
Comment 9•4 years ago
•
|
||
(In reply to Fair9 from comment #8)
Firefox should be a browser for the majority, not just for people who know how to make a backup of bookmarks.
Backups are automated, you don't have to do anything for Firefox to backup your bookmarks.
We can discuss at length about the fact the current UI doesn't help discovering backups, but that's a different kind of bug from a trashcan.
With that I don't mean that we think the current state is ok, the current state is not ok, but we think a trashcan is not the solution to that.
Description
•