09-20-2024 01:19 PM
I don't know what's changed, but I used to be able to drag a bunch of selected addresses in the address book to the BCC: (or other address field) in an email being composed.
Today, if I try to drag more than one address, it greys out most of the message and offers to add them as attachments.
Huh?
T'bird 128.2.3esr (64-bit) on W10
09-25-2024 12:36 PM
The silence is deafening. Is this perhaps the wrong place to ask?
09-27-2024 03:41 AM - edited 09-27-2024 03:52 AM
Hello
I can reproduce
An subject https://bugzilla.mozilla.org/show_bug.cgi?id=1913600
Try https://support.mozilla.org/en-US/kb/keyboard-shortcuts-thunderbird#w_writing-messages
Toggle Contacts Sidebar
I can not reproduce
09-27-2024 04:08 AM
Well it's nice to get an answer, but it's a confusing one. Can you or can you not reproduce the mess?
The referenced bug (1913600) seems to reproduce it quite nicely, down to the 0-length attachments one fewer than the number of address "dragged".
That seems to be marked closed, but I didn't notice any solution or work-around.
???
09-27-2024 04:30 AM - edited 09-27-2024 04:38 AM
Under 128.2.3, the same malfunction is currently occurring with Thunderbird bêta
For information purposes general, in my opinion, 132 is target bêta
Bêta, this is a pre-prod, a concern resolved in beta, may be resolved with one of the next Thunderbird release updates (for example) 128
In the meantime, try, Writing messages with Toggle Contacts Sidebar (by way of illustration) https://support.mozilla.org/en-US/kb/addressing-email#w_selecting-and-adding-recipients-from-contact...
09-27-2024 05:04 AM
I know I can select multiple addresses in the address book and click on Write.
But dragging multiple addresses to the email being written has always worked and is a bit more natural.
I don't understand the jargon above. This is apparently a newly introduced bug, to be fixed when?
10-02-2024 10:22 PM
Hello
132.0b1 currently and according to my tests, that's resolved
10-03-2024 04:03 AM
Forgive my unfamiliarity with the local jargon, but does that mean that an eventual (when?) update has fixed this bug?
10-17-2024 06:21 AM