Este site está com funcionalidades limitadas enquanto realizamos manutenção para melhorar sua experiência de uso. Se nenhum artigo resolver seu problema e você quiser fazer uma pergunta, nossa comunidade de suporte pode te ajudar em @FirefoxSupport no Twitter e /r/firefox no Reddit.

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Undo bug in Thunderbird 38.7.2

  • 1 resposta
  • 1 tem este problema
  • 1 exibição
  • Última resposta de Matt

more options

This is in regard to a problem with the undo feature sometimes losing the first item on the top of the stack when trying to undelete a message that is deleted by hitting the delete key. Recently, I deleted three messages one at a time and then decided that I wanted back the last of the three I deleted. Nothing happened when I did the first undo, subsequent undoes returned the second and third messages deleted but not the last one, the one that I wanted back.

This is in 38.7.2 running on OS X 10.11.4 and running with NIS 5 v5.9(35).

I have been having an issue with this problem for some time though, not sure when I noticed it though. Certainly it was happening before the most current 38.7.x and 10.11.4.

This is in regard to a problem with the undo feature sometimes losing the first item on the top of the stack when trying to undelete a message that is deleted by hitting the delete key. Recently, I deleted three messages one at a time and then decided that I wanted back the last of the three I deleted. Nothing happened when I did the first undo, subsequent undoes returned the second and third messages deleted but not the last one, the one that I wanted back. This is in 38.7.2 running on OS X 10.11.4 and running with NIS 5 v5.9(35). I have been having an issue with this problem for some time though, not sure when I noticed it though. Certainly it was happening before the most current 38.7.x and 10.11.4.

Todas as respostas (1)

more options

I suggest you file a bug report and include the steps to reproduce.

See https://bugzilla.mozilla.org