Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

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

  • 3 відповіді
  • 1 має цю проблему
  • 1 перегляд
  • Остання відповідь від 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?

Змінено Wayne Mery

Обране рішення

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

Читати цю відповідь у контексті 👍 0

Усі відповіді (3)

more options

Вибране рішення

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.