> I think I will definitely remove the current UI for mail.default_html_action in this bug. I am objecting to that. This UI must stay. Some of our users care a lot and have very strong opinions about this (in either direction), and many will be very upset to have this option gone. This preference UI must stay. > The current UI describes it as ... Yes, as I said, the intro label must change. I think the text was wrong anyways, even before this change. If you are lacking appropriate translatable strings, you may completely remove the intro text. If really necessary, the dropdown options alone are sufficient. > Personally, I would like to remove mail.default_html_action entirely We would massively lose users, in the following years. Because exactly our strongest advocates, the people who advocate for Thunderbird to be used in their families, friends, companies, they care a lot about this specific preference. It must stay, with UI. > I also think it is weird that this is a global preference, rather than per-account like "Compose messages in HTML format". The latter should probably be global as well (but it's irrelevant to this bug). Nobody wants to use 2 different text editors with completely different behaviors, in the same program. IIRC, the composer pref was originally made per-account, because we wanted to default newsgroup accounts to plaintext editor. But that makes little sense today. FWIW, almost nobody, not even die-hard plaintext fans, use the plaintext editor. Pretty much everybody uses the HTML editor, even for sending plaintext.
Bug 1727493 Comment 42 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> I think I will definitely remove the current UI for mail.default_html_action in this bug. I am objecting to that. This UI must stay (or rather moved to a new place). Some of our users care a lot and have very strong opinions about this (in either direction), and many will be very upset to have this option gone. This preference UI must stay. > The current UI describes it as ... Yes, as I said, the intro label must change. I think the text was wrong anyways, even before this change. If you are lacking appropriate translatable strings, you may completely remove the intro text. If really necessary, the dropdown options alone are sufficient. > Personally, I would like to remove mail.default_html_action entirely We would massively lose users, in the following years. Because exactly our strongest advocates, the people who advocate for Thunderbird to be used in their families, friends, companies, they care a lot about this specific preference. It must stay, with UI. > I also think it is weird that this is a global preference, rather than per-account like "Compose messages in HTML format". The latter should probably be global as well (but it's irrelevant to this bug). Nobody wants to use 2 different text editors with completely different behaviors, in the same program. IIRC, the composer pref was originally made per-account, because we wanted to default newsgroup accounts to plaintext editor. But that makes little sense today. FWIW, almost nobody, not even die-hard plaintext fans, use the plaintext editor. Pretty much everybody uses the HTML editor, even for sending plaintext.
> I think I will definitely remove the current UI for mail.default_html_action in this bug. I am objecting to that. This UI must stay (moved to a new place). Some of our users care a lot and have very strong opinions about this (in either direction), and many will be very upset to have this option gone. This preference UI must stay. > The current UI describes it as ... Yes, as I said, the intro label must change. I think the text was wrong anyways, even before this change. If you are lacking appropriate translatable strings, you may completely remove the intro text. If really necessary, the dropdown options alone are sufficient. > Personally, I would like to remove mail.default_html_action entirely We would massively lose users, in the following years. Because exactly our strongest advocates, the people who advocate for Thunderbird to be used in their families, friends, companies, they care a lot about this specific preference. It must stay, with UI. > I also think it is weird that this is a global preference, rather than per-account like "Compose messages in HTML format". The latter should probably be global as well (but it's irrelevant to this bug). Nobody wants to use 2 different text editors with completely different behaviors, in the same program. IIRC, the composer pref was originally made per-account, because we wanted to default newsgroup accounts to plaintext editor. But that makes little sense today. FWIW, almost nobody, not even die-hard plaintext fans, use the plaintext editor. Pretty much everybody uses the HTML editor, even for sending plaintext.
> I think I will definitely remove the current UI for mail.default_html_action in this bug. I am objecting to that. We need this preference UI (of course moved to a new place). Some of our users care a lot and have very strong opinions about this (in either direction), and many will be very upset to have this option gone. We cannot live without that UI for that preference. > The current UI describes it as ... Yes, as I said, the intro label must change. I think the text was wrong anyways, even before this change. If you are lacking appropriate translatable strings, you may completely remove the intro text. If really necessary, the dropdown options alone are sufficient. > Personally, I would like to remove mail.default_html_action entirely We would massively lose users, in the following years. Because exactly our strongest advocates, the people who advocate for Thunderbird to be used in their families, friends, companies, they care a lot about this specific preference. It must stay, with UI. > I also think it is weird that this is a global preference, rather than per-account like "Compose messages in HTML format". The latter should probably be global as well (but it's irrelevant to this bug). Nobody wants to use 2 different text editors with completely different behaviors, in the same program. IIRC, the composer pref was originally made per-account, because we wanted to default newsgroup accounts to plaintext editor. But that makes little sense today. FWIW, almost nobody, not even die-hard plaintext fans, use the plaintext editor. Pretty much everybody uses the HTML editor, even for sending plaintext.
> I think I will definitely remove the current UI for mail.default_html_action in this bug. I am objecting to that. We need this preference UI (of course moved to a new place). Some of our users care a lot and have very strong opinions about this (in either direction), and many will be very upset to have this option gone. We cannot live without UI for that preference. > The current UI describes it as ... Yes, as I said, the intro label must change. I think the text was wrong anyways, even before this change. If you are lacking appropriate translatable strings, you may completely remove the intro text. If really necessary, the dropdown options alone are sufficient. > Personally, I would like to remove mail.default_html_action entirely We would massively lose users, in the following years. Because exactly our strongest advocates, the people who advocate for Thunderbird to be used in their families, friends, companies, they care a lot about this specific preference. It must stay, with UI. > I also think it is weird that this is a global preference, rather than per-account like "Compose messages in HTML format". The latter should probably be global as well (but it's irrelevant to this bug). Nobody wants to use 2 different text editors with completely different behaviors, in the same program. IIRC, the composer pref was originally made per-account, because we wanted to default newsgroup accounts to plaintext editor. But that makes little sense today. FWIW, almost nobody, not even die-hard plaintext fans, use the plaintext editor. Pretty much everybody uses the HTML editor, even for sending plaintext.
> I think I will definitely remove the current UI for mail.default_html_action in this bug. I am objecting to that. We need this preference UI (of course moved to a new place). Some of our users care a lot and have very strong opinions about this (in either direction), and many will be very upset to have this option gone. We cannot live without UI for that preference. > The current UI describes it as ... Yes, as I said, the intro label of course needs to change. I think the text was wrong anyways, even before this change. If you are lacking appropriate translatable strings, you could completely remove the intro text. If really necessary, the dropdown options alone are sufficient. > Personally, I would like to remove mail.default_html_action entirely We would massively lose users, in the following years. Because exactly our strongest advocates, the people who advocate for Thunderbird to be used in their families, friends, companies, they care a lot about this specific preference. It must stay, with UI. > I also think it is weird that this is a global preference, rather than per-account like "Compose messages in HTML format". The latter should probably be global as well (but it's irrelevant to this bug). Nobody wants to use 2 different text editors with completely different behaviors, in the same program. IIRC, the composer pref was originally made per-account, because we wanted to default newsgroup accounts to plaintext editor. But that makes little sense today. FWIW, almost nobody, not even die-hard plaintext fans, use the plaintext editor. Pretty much everybody uses the HTML editor, even for sending plaintext.
> I think I will definitely remove the current UI for mail.default_html_action in this bug. I am objecting to that. We need this preference UI (of course moved to a new place). Some of our users care a lot and have very strong opinions about this (in either direction), and many will be very upset to have this option gone. We cannot live without UI for that preference. > The current UI describes it as ... Yes, as I said, the intro label of course needs to change. I think the text was wrong anyways, even before this change. If you are lacking appropriate translated strings, you could completely remove the intro text. If really necessary, the dropdown options alone are sufficient. > Personally, I would like to remove mail.default_html_action entirely We would massively lose users, in the following years. Because exactly our strongest advocates, the people who advocate for Thunderbird to be used in their families, friends, companies, they care a lot about this specific preference. It must stay, with UI. > I also think it is weird that this is a global preference, rather than per-account like "Compose messages in HTML format". The latter should probably be global as well (but it's irrelevant to this bug). Nobody wants to use 2 different text editors with completely different behaviors, in the same program. IIRC, the composer pref was originally made per-account, because we wanted to default newsgroup accounts to plaintext editor. But that makes little sense today. FWIW, almost nobody, not even die-hard plaintext fans, use the plaintext editor. Pretty much everybody uses the HTML editor, even for sending plaintext.
> I think I will definitely remove the current UI for mail.default_html_action in this bug. I am objecting to that. We need this preference UI (of course moved to a new place). Some of our users care a lot and have very strong opinions about this (in either direction), and many will be very upset to have this option gone. We cannot live without UI for that preference. > The current UI describes it as ... Yes, as I said, the intro label of course needs to change. I think the text was wrong anyways, even before this change. If you are lacking appropriate translated strings, you could completely remove the intro text. If really necessary, the dropdown options alone are sufficient. > Personally, I would like to remove mail.default_html_action entirely We would massively lose users, in the following years. Because exactly our strongest advocates, the people who advocate for Thunderbird to be used in their families, friends, companies, they care a lot about this specific preference. We need it, with UI. > I also think it is weird that this is a global preference, rather than per-account like "Compose messages in HTML format". The latter should probably be global as well (but it's irrelevant to this bug). Nobody wants to use 2 different text editors with completely different behaviors, in the same program. IIRC, the composer pref was originally made per-account, because we wanted to default newsgroup accounts to plaintext editor. But that makes little sense today. FWIW, almost nobody, not even die-hard plaintext fans, use the plaintext editor. Pretty much everybody uses the HTML editor, even for sending plaintext.
> I think I will definitely remove the current UI for mail.default_html_action in this bug. I am objecting to that. We need this preference UI (of course moved to a new place). Some of our users care a lot and have very strong opinions about this (in either direction), and many will be very upset to have this option gone. We cannot live without UI for that preference. > The current UI describes it as ... Yes, as I said, the intro label of course needs to change. I think the text was wrong anyways, even before this change. If you are lacking appropriate translated strings, you could completely remove the intro text. If really necessary, the dropdown options alone are sufficient. > Personally, I would like to remove mail.default_html_action entirely We would massively lose users, in the following years. Because exactly our strongest advocates, the people who advocate for Thunderbird to be used in their families, friends, companies, they care a lot about this specific preference. We need the pref, with UI. > I also think it is weird that this is a global preference, rather than per-account like "Compose messages in HTML format". The latter should probably be global as well (but it's irrelevant to this bug). Nobody wants to use 2 different text editors with completely different behaviors, in the same program. IIRC, the composer pref was originally made per-account, because we wanted to default newsgroup accounts to plaintext editor. But that makes little sense today. FWIW, almost nobody, not even die-hard plaintext fans, use the plaintext editor. Pretty much everybody uses the HTML editor, even for sending plaintext.