Closed Bug 1167434 Opened 9 years ago Closed 5 years ago

hitting enter in To/Cc (with filled fields below) should add a new empty addressing field of the same type as the cursor was in

Categories

(Thunderbird :: Message Compose Window, enhancement)

31 Branch
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: herter, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 Build ID: 20150504194141 Steps to reproduce: Create a new, reply to or forward an email. While in compose window, navigate cursor to any To:, Cc: or Bcc: field. Press Enter, in order to obtain a next open empty field. Actual results: Focus shifts to the next field existing. That forces to press enter many times, to the last field, and than Thunderbird opens finally a new empty field for another address, BUT of the type of the last field, and NOT of the type of the field from which we started to type the enter. That forces to change the type of the field to the desired To/CC/Bcc. Expected results: Thunderbird should open an empty field of the same type on which we typed the Enter. For example: To: MickyMouse@domain.any <-- cursor points to this field, press Enter Bcc: Myself@home.any For many years this worked correctly. The result should be: To: MickyMouse@domain.any To: [awaiting your entry] <-- enter the additional address, e.g. DonaldDuck@domain.any Bcc: Myself@home.any Etc. Always we should obtain an empty field for entry of the type To/CC/Bcc on which we typed "enter".
like bug 1167429, does this happen in safe mode? https://support.mozilla.org/en-US/kb/safe-mode
Flags: needinfo?(herter)
Summary: The 'To/cc' address entry does not work properly → hitting enter in To/Cc (with filled fields below) should add a new empty addressing field of the same type as the cursor was in, not of the last type
This looks to me like an enhancement request so no safe mode test needed. However it is probably a waste of effort if the compose addressing rework (into the 3 Outlook-like rows) is done soon.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Component: Untriaged → Message Compose Window
Ever confirmed: true
Flags: needinfo?(josiah)
Flags: needinfo?(bwinton)
OS: Unspecified → All
Hardware: Unspecified → All
Yeah, that seems like what we want to happen. (If that's what you were asking me. If you were asking me how long it's going to be until we get the new compose addresser, I have no idea. ;)
Flags: needinfo?(bwinton)
I do not see it an enhancement request. This functionally _used to be_ in Thunderbird for many years, it got lost a while ago, approximately when the version's were changed from n.m, n.m+1 etc to the new high primary version convention. I do not know how to better pinpoint the time, when the problem occurred.
Flags: needinfo?(herter)
As for the new compose addresser, probably a while before that's implemented. I myself am pretty much unable to do TB development between school, work, and reviews. So someone with some time needs to attempt it. I'm not sure who that would be though. Paenglab?
Flags: needinfo?(josiah)

(In reply to :aceman from comment #2)

This looks to me like an enhancement request so no safe mode test needed.

However it is probably a waste of effort if the compose addressing rework
(into the 3 Outlook-like rows) is done soon.

...wrote Aceman 5 years ago. Yeah soonish. Soon is a relative term wrt Thunderbird. That said, the "compose addressing rework" has now happened (bug 440377), which makes this wontfix. Even without bug 440377, I'm not sure if pressing Enter on an existing recipient should really create a blank recipient line between existing recipients as this bug proposed. Maybe.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Summary: hitting enter in To/Cc (with filled fields below) should add a new empty addressing field of the same type as the cursor was in, not of the last type → hitting enter in To/Cc (with filled fields below) should add a new empty addressing field of the same type as the cursor was in
You need to log in before you can comment on or make changes to this bug.