Closed Bug 1613090 Opened 4 years ago Closed 4 years ago

First available recipient input defaults to BCC instead of To when changing sender to non-default identity with auto-bcc-address

Categories

(Thunderbird :: Message Compose Window, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: anjeyelf, Unassigned)

References

Details

(Keywords: regression)

User Story

New minimal STR (confirmed on 68.5.0 (32-Bit), pre-pills)

1) Have mail account where:
- default identity *without* auto-bcc
- non-default identity *with* auto-bcc (for details, see comment 0)
2) compose new msg with default identity (correctly showing only empty To-field for input)
3) change sender to non-default identity having auto-bcc, observe the following empty recipient row which is available for input

Actual
- after changing sender, empty recipient row for input (below the auto-BCC) has also changed to BCC

Expected
- first empty available input row after auto-BCC should default to To (as it does for default identities having auto-bcc)

Reported as a regression (per comment 3):
Thunderbird 68.2.1: no bug (default is "To")
Thunderbird 68.3.0: bug (default is CC/BCC)

Maybe regressed by this bug which fixed the reverse problem:
Bug 1504455 - Composition: Pressing ENTER on BCC recipient with comma in display name creates a new recipient row of type "To" instead of "Bcc"

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0

Steps to reproduce:

Windows 10 OS
Thunderbird version 68.4.2

In Account Settings window
Select mail account name in left pane
click on 'Manage identities' button
Select any non default identity (Not an identity set as default)
Under 'Copies & Folders' select 'Bcc these email addresses:' and enter an email address.
click on all the OKs

Click on Write
select the non default identity as 'From'
Bcc email address is auto entered....as expected.

Actual results:

However, the next field below is auto set to 'Bcc'.
There is no auto display of an empty 'To' field below the preset Bcc. So, you always have to manually change the bcc to TO.
Note: this does not occur if you set an auto Bcc with the 'default' identity. In that instance, the auto Bcc is displayed with an empty TO field below.

Expected results:

The non default identity selected in 'From' should auto display the Bcc as set...so far this is ok....but below that Bcc, the next field should be automatically an empty 'To' field.

In addition....
whilst in same Write window, if you then change the 'From' from the non default identity to any other email address (which dose not have a 'Bcc these email addresses:'',) the auto bcc entered email address disappears...this is expected, but you are still left with an empty auto Bcc field. There is no auto 'TO' field for you to use. It has to be manually selected.

Please note this only occurs when a mail account has additional non default identities and specifically it is those non default identites that have the 'Bcc these email addresses:' selected.

Tested in Safe Mode with same results.

This issue was brought to my attention when someone posted in support forum and I tested their issue and discovered I could replicate 100%.
https://support.mozilla.org/en-US/questions/1278956

Further to first commnet:
In addition....
whilst in same Write window, if you then change the 'From' from the non default identity to any other mail account default identity email address which also has a 'Bcc these email addresses:'' but a different email address .
The auto bcc entered email address changes...this is expected, but you are still left with an empty auto Bcc field. There is no auto 'TO' field for you to use. It has to be manually selected.

If you never use a non default identity, only mail accounts set with one default identity, then this issue never occurs.

Please note further testing shows the same problem as described previously also occurs when a non default identity is set up with a 'Cc these email addresses:', the next empty field now only shows a 'Cc' field instead of an empty 'To' field.

I'm having the same bug on Linux (openSUSE-15.1) and it seems to be a regression.
Thunderbird 68.2.1: no bug (default is "To")
Thunderbird 68.3.0: bug (default is CC/BCC)

Maybe related: bug 1616514

(In reply to MD-Work from comment #3)

Maybe related: bug 1616514

Thanks, but they cannot be related. bug 1616514 is a request for enhancement (not yet implemented) of a feature which hasn't even arrived on your release versions yet (recipient "pills").

Status: UNCONFIRMED → NEW
User Story: (updated)
Component: Untriaged → Message Compose Window
Ever confirmed: true
Keywords: regression
See Also: → 1504455
Summary: non default identity 'bcc these email addresses' does not auto show a TO → First available recipient input defaults to BCC instead of To when changing sender to non-default identity with auto-bcc-address

Anje, thank you for reporting this!

I appreciate that it's annoying for those affected, sorry for that. The behaviour is wrong, but the UI communicates the odd state correctly. As a workaround, it's two clicks (once) on the first recipient type dropdown selector to change BCC back to To. Thereafter, new rows will keep To flavor.

The good news is, this problem will go away soon (*) with the redesigned recipient field of TB 78, where we'll have one dedicated field for all recipients of each type. So I think, to be honest, we probably wouldn't want to invest precious developer time into fixing this flaw in the old design of TB 68 which is on the way out (a bit longer on ESR, but still...). So imo this looks like wontfix for TB 68.

Alex will make the call.

(*) The target release date for Thunderbird 78.0 final is 2020-06-30.

Flags: needinfo?(alessandro)

This is one of the many shortcomings of the old addressing field, and it was designed to behave like this (remembering the previous recipient type and using that when adding a new row).

I doubt we want to change this since 78 is coming out in a month or so.

Flags: needinfo?(alessandro)
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX

Thanks for feedback. Understand it has been looked into and will get resolved in 78. Many thanks.

You need to log in before you can comment on or make changes to this bug.