1743794 - In-Reply-To, Message-Id headers (mail-messageids-headerfield elements) are empty

Status: RESOLVED DUPLICATE of bug 1764652

(Thunderbird :: Mail Window Front End, defect)

Description

[Henry Wilkes (they/them) [:henry-x]]

Steps to reproduce

1. Set the mailnews.headers.extraExpandedHeaders preference to "message-id in-reply-to".
2. Restart thunderbird.
3. Select a message.

Result

The message header fields are empty (you just see an expander). Also, if you click the expander, you get the following error

Uncaught TypeError: can't access property "length", this.headerValue.children is undefined
    _toggleWrap chrome://messenger/content/mailWidgets.js:317
    connectedCallback chrome://messenger/content/mailWidgets.js:303

This is because the <mail-messageids-headerfield> headerValue property is initialised as a XULElement https://searchfox.org/comm-central/rev/7a159d31ba0048f86b74e0366040ea13b8c26a4c/mail/base/content/widgets/mailWidgets.js#307 but is set to a string here https://searchfox.org/comm-central/rev/7a159d31ba0048f86b74e0366040ea13b8c26a4c/mail/base/content/msgHdrView.js#1239

Expect

The header values to be shown. This is probably meant to have a headerValue setter, like https://searchfox.org/comm-central/rev/7a159d31ba0048f86b74e0366040ea13b8c26a4c/mail/base/content/widgets/mailWidgets.js#70

Comment 1

[Alessandro Castellani [:aleca]]

Good finding and great analysis.
All those Custom elements header fields should be converted into pure HTML and their internal structure should be drastically simplified.

Comment 2

[Alessandro Castellani [:aleca]]

This was fixed by the work done on bug 1764652.