1819777 - Printing selected message did nothing, console error: Uncaught (in promise) TypeError: messageBrowser.contentWindow.content is null

Status: RESOLVED FIXED

(Thunderbird :: Message Reader UI, defect, P3)

Description

[Thomas D. (:thomas8)]

From my smoketesting of Beta 111.0b2 (64-bit) en-US, Win10 (intermittent, couldn't reproduce later, but still seeing the old error message in console):

STR

• Selected a random message
• Pressed Ctrl+P

Actual result

• nothing
• console error:

Uncaught (in promise) TypeError: messageBrowser.contentWindow.content is null
    <anonymous> chrome://messenger/content/about3Pane.js:3673
    doCommand chrome://messenger/content/mailCommon.js:545
    goDoCommand chrome://messenger/content/globalOverlay.js:100
    oncommand chrome://messenger/content/messenger.xhtml:1
about3Pane.js:3673:1

Expected result:

• Print dialog for the selected message

Comment 2

[Wayne Mery (:wsmwk)]

This bug is reported against 111.0b2, and bug 1816294's patch is included in in 111.0b2.
Why would this bug be considered a duplicate of bug 1816294, do you expect Geoff to reopen 1816294?

Comment 3

[Magnus Melin [:mkmelin]]

Ah, didn't realize that. Maybe this one is still valid then.

Comment 4

[Geoff Lankow (:darktrojan) [OOO, back 5 Jan]]

WFM.

Comment 5

[Wayne Mery (:wsmwk)]

Does this still reproduce with nightly?

Comment 6

[Thomas D. (:thomas8)]

(In reply to Wayne Mery (:wsmwk) from comment #5)

Does this still reproduce with nightly?

Yes. Trying to print (Ctrl+P) on a running Daily 113.0a1 (2023-03-26) (64-bit), Win10, gmail-IMAP repeatedly failed with the error below. The TB session was running at least a day, probably across "Suspend to disk" and "Sleep".
However, still intermittent: Weird, after restarting TB, it works. Same message.

Uncaught (in promise) TypeError: can't access property "browsingContext", messageBrowser.contentWindow.content is null
    <anonymous> chrome://messenger/content/about3Pane.js:4452
    doCommand chrome://messenger/content/mailCommon.js:590
    goDoCommand chrome://messenger/content/globalOverlay.js:100
    oncommand chrome://messenger/content/messenger.xhtml:1
about3Pane.js:4452:1

Comment 7

[Geoff Lankow (:darktrojan) [OOO, back 5 Jan]]

Attachment: Bug 1819777 - Use `getMessagePaneBrowser()` instead of `content` when printing. r=#thunderbird-reviewers

Comment 8

[Geoff Lankow (:darktrojan) [OOO, back 5 Jan]]

I don't know why .content is sometimes unreliable, but it is.

Comment 9

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/comm-central/rev/ae0cc090ff0d
Use getMessagePaneBrowser() instead of content when printing. r=aleca

Comment 10

[Wayne Mery (:wsmwk)]

Comment on attachment 9325331 [details]
Bug 1819777 - Use getMessagePaneBrowser() instead of content when printing. r=#thunderbird-reviewers

[Triage Comment]
Approved for beta

Comment 11

[Rob Lemley [:rjl]]

Thunderbird 112.0b5:
https://hg.mozilla.org/releases/comm-beta/rev/e7a4ee976b4f