Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Undo no longer includes undeleting a recently deleted email with the update to 115. SOLVED caused by ConfirmBeforeDelete add-on.

  • 3 risposte
  • 1 ha questo problema
  • 7 visualizzazioni
  • Ultima risposta di TheSa|nt

more options

Just recently upgraded to v115 (115.5.0)

I noticed that Edit->Undo will undo moved messages and stuff, but not deleted messages. So if you send a message to the trash and hit undo, it won't undo that. Instead, it will undo whatever you did before it (or won't undo anything if you haven't done anything else since opening TB).

Or is that just me?

Just recently upgraded to v115 (115.5.0) I noticed that Edit->Undo will undo moved messages and stuff, but not deleted messages. So if you send a message to the trash and hit undo, it won't undo that. Instead, it will undo whatever you did before it (or won't undo anything if you haven't done anything else since opening TB). Or is that just me?

Modificato da Wayne Mery il

Soluzione scelta

Nevermind. This seemed to be caused by the ConfirmBeforeDelete plugin. A conflict between the new TB and it.

Leggere questa risposta nel contesto 👍 0

Tutte le risposte (3)

more options

Soluzione scelta

Nevermind. This seemed to be caused by the ConfirmBeforeDelete plugin. A conflict between the new TB and it.

more options

TheSa|nt said

Nevermind. This seemed to be caused by the ConfirmBeforeDelete plugin. A conflict between the new TB and it.

Interesting. Thanks for posting that information here!

Have you informed the add-on author?

more options

Wayne Mery said

TheSa|nt said

Nevermind. This seemed to be caused by the ConfirmBeforeDelete plugin. A conflict between the new TB and it.

Interesting. Thanks for posting that information here!

Have you informed the add-on author?

I did via their Github issues tab. Nothing has come of it yet, so they might not have seen it.