Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

"Close message window/tab on move or delete" does not seem to work.

  • 2 antwurd
  • 1 hat dit probleem
  • 189 werjeftes
  • Lêste antwurd fan TomHackett
  • Oplost

I am running TB 66.0b2 on MAC Mojave 10.14.3. Prior to beta 2, whenever I filed or deleted an open message, the tab in which it was displayed closed. Now, when I file or delete an open message, it just sits there. I went into Preferences > Display > Advanced and noted that the check box "Close message window/tab on move or delete" was not checked. I checked it and restarted TB. Now the box remains checked, but the function does not seem to work. This is a minor annoyance, but it is an annoyance.

I am running TB 66.0b2 on MAC Mojave 10.14.3. Prior to beta 2, whenever I filed or deleted an open message, the tab in which it was displayed closed. Now, when I file or delete an open message, it just sits there. I went into Preferences > Display > Advanced and noted that the check box "Close message window/tab on move or delete" was not checked. I checked it and restarted TB. Now the box remains checked, but the function does not seem to work. This is a minor annoyance, but it is an annoyance.

Keazen oplossing

My understanding is that issues identified in beta testing are supposed to be reported as a bug in Bugzilla. If you are not beta testing you probably should be using the release version of the software.

https://bugzilla.mozilla.org/

Dit antwurd yn kontekst lêze 👍 1

Alle antwurden (2)

Keazen oplossing

My understanding is that issues identified in beta testing are supposed to be reported as a bug in Bugzilla. If you are not beta testing you probably should be using the release version of the software.

https://bugzilla.mozilla.org/

This appears to have been reported by someone else on bugzilla. It is said to be a "known regression in TB66."