getting multiple "Use Bcc instead" warnings when replying
Categories
(Thunderbird :: Message Compose Window, defect, P1)
Tracking
(thunderbird_esr91+ fixed, thunderbird93+ verified)
People
(Reporter: redadder, Assigned: mkmelin)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [TM: 91.1.1])
Attachments
(3 files, 1 obsolete file)
294.52 KB,
image/jpeg
|
Details | |
48 bytes,
text/x-phabricator-request
|
wsmwk
:
approval-comm-beta+
wsmwk
:
approval-comm-esr91+
|
Details | Review |
2.11 KB,
patch
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0
Steps to reproduce:
Reply to all with 20 recipients
Actual results:
Multiple Warnings popped up do you want to "Use Bcc instead" or "Keep Recipients public"
see attached photo
You can pick one of the warnings but no more
There were 20 recipients even though it shows Warnings for just 15 to 20
Expected results:
I'd expect just one warning where you pick what option you want to use
and maybe somewhere in Preferences to turn this off
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
I think this used to work, but proton made the notifications not stack on top of eachother...
Lasana, please have a look asap.
Comment 2•3 years ago
|
||
Seems to be caused by the changes in bug 1717127. The checkPublicRecipients()
was made async (for localization!) but not awaited on in the mutation observer. However that will likely still cause this bug because checkPublicRecipients()
being async means subsequent calls to this function can run before the prior finishes as it waits for the l10n value in the "next tick". Thus causing the notification to not be seen the second time around. I'm changing it back to sync for now.
PS: In my humble opinion, calling async functions from sync ones is bad practice, except in a few specific cases.
Comment 3•3 years ago
|
||
This function can get called multiple times, being async will allow
calls to preempt each other resulting in more than one notification.
Assignee | ||
Comment 4•3 years ago
|
||
The test started failing with "cardDetails", aDocumentNode is undefined. For what's done in testMailingListMembersCounted there won't be a document. I don't know why it seemed to work before... Stack like
updateExtraAddressProcessing@chrome://messenger/content/mailWidgets.js:1282:39
OnAddressBookDataChanged/<@chrome://messenger/content/msgHdrView.js:438:34
OnAddressBookDataChanged@chrome://messenger/content/msgHdrView.js:432:28
observe@chrome://messenger/content/msgHdrView.js:409:33
dropCard@resource:///modules/AddrBookDirectory.jsm:542:18
addCard@resource:///modules/AddrBookDirectory.jsm:423:17
addCard@resource:///modules/AddrBookMailingList.jsm:213:31
Assignee | ||
Updated•3 years ago
|
Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/04fe84062d16
make sure to show only one bulk mail notification. r=lasana
Assignee | ||
Comment 6•3 years ago
|
||
Comment on attachment 9238914 [details]
Bug 1727862 - make sure to show only one bulk mail notification. r=lasana
[Approval Request Comment]
Regression caused by (bug #): bug 1717127
User impact if declined: unreasonable amount of notification bars when replying to many
Testing completed (on c-c, etc.): c-c
Risk to taking this patch (and alternatives if risky): not risky
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Updated•3 years ago
|
Comment 7•3 years ago
|
||
Comment on attachment 9238914 [details]
Bug 1727862 - make sure to show only one bulk mail notification. r=lasana
[Triage Comment]
Approved for beta
Comment 8•3 years ago
|
||
Let's schedule to get this for 92.1.1
Comment 9•3 years ago
|
||
bugherder uplift |
Thunderbird 93.0b1:
https://hg.mozilla.org/releases/comm-beta/rev/b6845202357e
Comment 10•3 years ago
|
||
93.0b1 build2 worked for me. thanks for the fix.
Reporter | ||
Comment 11•3 years ago
|
||
Yes worked for me as well - thanks to all involved
Updated•3 years ago
|
Comment 12•3 years ago
|
||
Comment on attachment 9238914 [details]
Bug 1727862 - make sure to show only one bulk mail notification. r=lasana
[Triage Comment]
Approved for esr91
Comment 13•3 years ago
|
||
This cannot be uplifted to 91 with the D124197. It builds upon changes from bug 1707801, which included the "many-public-recipients-notice" that is used in this patch.
I think using "many-public-recipients-info" will work. Lasana can you confirm that and make a patch for c-esr91?
Comment 14•3 years ago
•
|
||
I didn't do the fix for this but maybe we should uplift bug 1707801 as well. It landed on 93, can we?
Assignee | ||
Comment 15•3 years ago
|
||
I didn't build and test 91, but this should be the minimal fix there.
Comment 16•3 years ago
|
||
Rob, I can test the esr patch before shipping, once we have a candidate build
Comment 17•3 years ago
|
||
I think we should land the other patch so that if there are any more issues in this area we don't have to keep doing esr only versions.
Comment 18•3 years ago
|
||
bugherder uplift |
Thunderbird 91.1.1:
https://hg.mozilla.org/releases/comm-esr91/rev/74ecf9f3aa67
Description
•