Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

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.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

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

  • 2 replies
  • 1 has this problem
  • 1 view
  • Last reply by TomHackett

TomHackett
TomHackett
more options

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.

Chosen solution

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/

Read this answer in context 👍 1

All Replies (2)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

Chosen Solution

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/

TomHackett
TomHackett Question owner
more options

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