Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

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

  • 2 yanıt
  • 1 kişi bu sorunu yaşıyor
  • 1 gösterim
  • Son yanıtı yazan: 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.

Seçilen çözüm

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/

Bu yanıtı konu içinde okuyun 👍 1

Tüm Yanıtlar (2)

more options

Seçilen çözüm

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/

more options

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