1867466 - Reply window not opening (failure code: 0x80004005 [nsIMsgComposeService.OpenComposeWindow])

Status: UNCONFIRMED

(Thunderbird :: Message Compose Window, defect)

Description

[juangdse]

Steps to reproduce:

go to some message and hit 'Reply'

Actual results:

nothing

Expected results:

reply-to window opens

The 'Foreward' window does work.

Comment 1

[Ruth Milner]

Recently upgraded to TB 115. Am now on 115.7.0 (32-bit), upgraded within TB from 102, and have noticed the reported behavior >90% of the time when attempting to reply to a message, i.e. select any of the methods for replying to a message you're viewing and nothing happens:

• click on Reply button in the message header pane
• right-click on message body or subject line and select "Reply" (sender or all)
• click on Reply or Reply All in the toolbar
• go to the "Message" item in the window menu bar and select either Reply option
• (on Windows) use alt-M alt-R as shortcut to Message Reply

All of these actions produce no response at all. UNTIL I open the Error Console. (SO MANY ERRORS!!!) There I can see that most of the above actions produce errors like these:

Uncaught (in promise) NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgComposeService.OpenComposeWindow]
ComposeMessage chrome://messenger/content/mailCommands.js:436
_composeMsgByType chrome://messenger/content/mailCommon.js:792
doCommand chrome://messenger/content/mailCommon.js:701
cmd_reply chrome://messenger/content/mailCommon.js:94
doCommand chrome://messenger/content/mailCommon.js:729
doCommand chrome://messenger/content/mailTabs.js:305
doCommand chrome://messenger/content/tabmail.js:578
goDoCommand chrome://messenger/content/globalOverlay.js:99
oncommand chrome://messenger/content/messenger.xhtml:1
mailCommands.js:436

Uncaught (in promise) NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgComposeService.OpenComposeWindow]
ComposeMessage chrome://messenger/content/mailCommands.js:436
_composeMsgByType chrome://messenger/content/mailCommon.js:792
doCommand chrome://messenger/content/mailCommon.js:701
doCommand chrome://messenger/content/mailTabs.js:305
doCommand chrome://messenger/content/tabmail.js:578
goDoCommand chrome://messenger/content/globalOverlay.js:99
oncommand chrome://messenger/content/messenger.xhtml:1
mailCommands.js:436

The exceptions are the Reply button in the header pane and the keyboard shortcut alt-M alt-R, which produce this warning instead:

window.controllers/Controllers is deprecated. Do not use it for UA detection.

Once a Reply method has produced that brief warning, any of the above Reply methods will now successfully open a compose window to reply in, as expected, but ONLY FOR THAT MESSAGE, and ONLY ON THAT VIEWING, and ONLY WHILE THE ERROR CONSOLE IS OPEN. If I go look at a different message, I can't reply to that one until I take the above steps. If I go back to the message I previously viewed, I can no longer reply to it until I take the above steps. If I close the Error Console, or restart TB, I can't reply to any message until I open the Error Console and take the above steps.

This is utterly bizarre. I hope that these error messages are helpful.

Also, why is something in TB 115 using deprecated code? I thought this was essentially a ground-up rewrite?

Thanks for any help you can provide.