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

With Thunderbird 78, while creating a new message, I cannot Tab to the message body

  • 2 yanıt
  • 1 kişi bu sorunu yaşıyor
  • 1 gösterim
  • Son yanıtı yazan: HankFriedman

more options

After updating to Thunderbird 78 (and then 78.1), I can no longer use the tab key to move to the message body when writing an email.

And also the Quicktext extension will only fill in the message body if I first click on the message body.

This is very annoying new behavior, and I tried going back to previous versions of Thunderbird but that wasn't allowed.

Can any one help me?

After updating to Thunderbird 78 (and then 78.1), I can no longer use the tab key to move to the message body when writing an email. And also the Quicktext extension will only fill in the message body if I first click on the message body. This is very annoying new behavior, and I tried going back to previous versions of Thunderbird but that wasn't allowed. Can any one help me?

Seçilen çözüm

Thank you so much for sharing that you weren't having the same issue.

That led me to testing all of my extensions to find the culprit.

It was the Prowritingaid extension that was messing things up.

I disabled it and now everything is working perfectly.

I will report this to the Prowritingaid folks.

Thanks again.

Hank

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

Tüm Yanıtlar (2)

more options

First, do you have the latest Quicktext for TB 78, v. 3.1?

https://addons.thunderbird.net/en-US/thunderbird/addon/quicktext/versions/

Second, does the Tab key move to the message body when Quicktext is disabled? I don't use Quicktext, but the Tab key works as expected.

more options

Seçilen çözüm

Thank you so much for sharing that you weren't having the same issue.

That led me to testing all of my extensions to find the culprit.

It was the Prowritingaid extension that was messing things up.

I disabled it and now everything is working perfectly.

I will report this to the Prowritingaid folks.

Thanks again.

Hank