Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

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

  • 3 respostas
  • 1 tem este problema
  • 7 visualizações
  • Última resposta por 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?

Modificado por Wayne Mery a

Solução escolhida

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

Ler esta resposta no contexto 👍 0

Todas as respostas (3)

more options

Solução escolhida

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.