"Always prefer display name over message header" checkbox is always checked
Categories
(Thunderbird :: Address Book, defect)
Tracking
(thunderbird_esr68 wontfix, thunderbird_esr78 fixed, thunderbird80 fixed)
People
(Reporter: darktrojan, Assigned: darktrojan)
References
Details
(Keywords: regression)
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
wsmwk
:
approval-comm-beta+
wsmwk
:
approval-comm-esr78+
|
Details | Review |
I think this got broken when we first linted abCard.js. We made one attempt to fix it at the time but it's still broken.
Assignee | ||
Comment 1•4 years ago
|
||
This puts the line back to how it was before we added linting. Obviously the linting change and the follow-up fix were both bogus.
Assignee | ||
Updated•4 years ago
|
Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/7405c52008fe
Fix "Always prefer display name over message header" checkbox. r=aleca
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Comment 3•4 years ago
|
||
Comment on attachment 9166718 [details]
Bug 1655884 - Fix "Always prefer display name over message header" checkbox. r?aleca
[Triage Comment]
Approved for beta
Comment 4•4 years ago
|
||
bugherder uplift |
Thunderbird 80.0b2:
https://hg.mozilla.org/releases/comm-beta/rev/e669b14b4f3b
Updated•4 years ago
|
Comment 5•4 years ago
|
||
Looks good to me in my testing of the 80.0b2 release candidate on Ubuntu 18.04.4.
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 6•4 years ago
|
||
Comment on attachment 9166718 [details]
Bug 1655884 - Fix "Always prefer display name over message header" checkbox. r?aleca
[Triage Comment]
Approved for esr78
Comment 7•4 years ago
|
||
bugherder uplift |
Thunderbird 78.2.0:
https://hg.mozilla.org/releases/comm-esr78/rev/12d95f4c66b9
Updated•4 years ago
|
Comment 8•4 years ago
•
|
||
Still being always checked in my testing of the 78.2.0 release candidate on Ubuntu 18.04.5 LTS. New profile.
Helps to test the correct build.
Comment 9•4 years ago
|
||
Well, maybe we should clarify the desired behaviour first because imho the design is inherently garbled and mutilated.
We have a global pref controlling the same behaviour: Show only display name for people in my address book.
Iiuc, here we have a per-card pref which is supposed to override the global behaviour.
If I don't change the card pref, it should use the global default, isn't it?
So what is the difference in UI state between per-card custom setting and "use global setting"? Can't tell.
Clearly, the interaction of global and per-card pref can never work correctly and predictably unless per-card pref is triple:
- Use global pref
- Prefer display name from address book over message header
- Prefer message header over address book display name
Internally, use a number pref which can be set to 0, 1, and 2.
And what if I want the display name from my AB AND the email address?
Updated•4 years ago
|
Description
•