為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Thunderbird 78 - how to show one address per line when authoring emails (TB 68 behaviour)

  • 3 回覆
  • 1 有這個問題
  • 2 次檢視
  • 最近回覆由 Wayne Mery

more options

Subject line sums it all up.

When authoring emails, I want to show one address-per line.

I do not want to have a bunch of addresses on one line with commas between them. I want a separate line per address, as per the previous behavior.

Please advise on how to accomplish this.

Subject line sums it all up. When authoring emails, I want to show one address-per line. I '''do not''' want to have a bunch of addresses on one line with commas between them. I want a separate line per address, as per the previous behavior. Please advise on how to accomplish this.

所有回覆 (3)

more options
I do not want to have a bunch of addresses on one line with commas between them.

That's fine. There are just a bunch of addresses on one line with no commas between them. Also see https://support.mozilla.org/en-US/kb/addressing-email

I want a separate line per address, as per the previous behavior.

You can't.

由 christ1 於 修改

more options

So, my only solution will be to revert to previous version of the software (which won't be seeing security updates), or start using different software. Thanks for the non-answer anyway.

Maybe one day, probably long after I'm dead, other developers will learn to not force UI/UX changes on users, without options to continue to use their preferences. I've always offered UI reversion options in my applications updates, it is not that hard to accomplish, merely requires actually caring about your users.

more options

That is a business choice that you are welcome of course do decide for yourself for your own code. We however cannot afford to arbitrarily keep large pieces (we're not talking about a few lines of code) of ten year old code throughout the code base that has been superseded. It's not a sustainable model, and long term not in the best interest of our users.