cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Yacht_Sailor
New member
Status: New idea

So scrolling through the list in your collection and one slight miss swipe and something is deleted. What was it? No idea. It just vanishes. It would be great if there was a confirm delete option before it disappears. 

19 Comments
phazzle
New member

why is it so easy to delete ff android collection items with an accidental swipe or a tap but then also impossible to undo?

Status changed to: New idea
Jon
Community Manager
Community Manager

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

ageo2366
New member

I use collections on android for easy access. However, I keep accidentally deleting with swipe when using phone with single hand. Would like a confirmation or even disable swipe delete for collections. 

YDS
New member

The collections is a great idea but very easy to accidently delete something. It would be great to have a confirm delete or another way to make deleting not so instant. 

Tommy5
New member

saved collections page deleted items

Just a suggestion- in the browser collections its currently really easy to mistakenly swipe right-even slightly- while scrolling through a collection list and inadvertantly delete items . Suggest adding a delete confirm stop before deleting.  Currently it Instantly deletes saved pages before you even know what it was.  

Status changed to: New idea
Jon
Community Manager
Community Manager

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

quinn_jones
New member

I've run into this exact issue a bunch of times.

There are too many ways to delete items.  The 'X' is sufficient, swiping is too quick and easy 

Diederik
Making moves

Confirming delete url from Collections? yes/no

Situation now:
When I use Collections, it often happens that I mistakenly remove the URL from collections and I experience that as very annoying.
I think many users feel the same way

Idea:
Create a new option rule in Firefox that reads "Confirming delete url from Collections? yes/no" and program Firefox as such.
When 'yes' is chosen and I then accidentally threaten to remove a url from collections, I first get the question "Remove the url?"
That saves a lot of annoyance..

Jon
Community Manager
Community Manager

(Note: similar ideas have been merged into this thread)

colleen
New member

This please!!!!! Recently deleted items, an undo button or making it harder to delete items would be very appreciated.

011001010100110
New member

This has been driving me crazy for a while 

You have a list of 30 pages in a collection and then one is deleted because of your swipe actions and you have nothing to remind yourself. So can't find it again. 

Koraxtu
New member

This issue has been bugging me for some months now.

I would like either:

  1. Recently deleted history
  2. For the horizontal delete swipe to require a new touch contact instead of transitioning from a vertical scroll swipe to a horizontal delete swipe with no pause
  3. For the horizontal delete swipe to be removed, there is already an 'X' button to delete. It doesn't need a gesture as well
mmjeres
New member

PLEASE!!!  I wish I had a dollar for every accidentally deleted link in a collection!  The ease of deleting information by accident with no convenient way to retrieve it greatly undermines the functionality of collections.

Hemlock_Stones
New member

Accidental swipe deletion from collections has been a problem for me as well.  An undo option would be desirable, and consistent with how swipe-to-delete works for tabs.  It should be possible to disable both features in settings.  

Frankly, the swipe-to-delete gestures feel like more bug than feature, as X-to-delete already handles this just fine.  Truly unnecessary feature bloat in Firefox Android.  Save it for your dating apps😉

andyross
Making moves

I am going to also STRONGLY suggest this needs fixing. I posted about this once before. And worse, it usually isn't one anywhere near where your finger currently is!!!!

It seems as if it only takes a 10-15% swipe before it triggers. That is WAY too little for a DELETE. I'm guessing this is just some standard library, and the amount of swipe needed before triggering something can be adjusted with a simple parameter change. Hopefully, someone who knows how to read the code can look into it and verify it a simple fix can at least make it harder to happen.