This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Undo bug in Thunderbird 38.7.2

  • 1 èsì
  • 1 ní ìṣòro yìí
  • 1 view
  • Èsì tí ó kẹ́hìn lọ́wọ́ 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.

All Replies (1)

more options

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

See https://bugzilla.mozilla.org