Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Learn More

Scary message delete behavior when content display blocked

  • 1 wótegrono
  • 1 ma toś ten problem
  • 3 naglědy
  • Slědne wótegrono wót 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.

Wubrane rozwězanje

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

Toś to wótegrono w konteksće cytaś 👍 0

Wšykne wótegrona (1)

more options

Wubrane rozwězanje

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