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

Scary message delete behavior when content display blocked

  • 1 resposta
  • 1 has this problem
  • 3 views
  • Last reply by wevdap

more options

In Thunderbird 1153.1 (MacOS), it appears that the "Delete" button next to the header information on a message whose content display is blocked per privacy settings is applied not to that individual message but rather to the folder containing it. There's (fortunately!!) a confirmation dialog warning that that entire folder would be deleted unrecoverably, but it seems non-intuitive and dangerous that the button's scope should change depending on the content display status. When the content is displayable, the button applies only to the individual message, as I'd expect.

In Thunderbird 1153.1 (MacOS), it appears that the "Delete" button next to the header information on a message whose content display is blocked per privacy settings is applied not to that individual message but rather to the folder containing it. There's (fortunately!!) a confirmation dialog warning that that entire folder would be deleted unrecoverably, but it seems non-intuitive and dangerous that the button's scope should change depending on the content display status. When the content is displayable, the button applies only to the individual message, as I'd expect.

Chosen solution

115.4.1 may have fixed this - on a quick check following an update, I'm not seeing this behavior.

Ler a resposta no contexto 👍 0

All Replies (1)

more options

Chosen Solution

115.4.1 may have fixed this - on a quick check following an update, I'm not seeing this behavior.