1569922 - conversation-browser.js - this.docShell is null

Status: RESOLVED WORKSFORME

(Thunderbird :: Instant Messaging, defect)

Description

[vtol]

• W10 Pro x_64 v1903 b18362.267
• Tb 69.0b1 (64-bit) en-GB

---

error console repeatedly prints:

TypeError: this.docShell is nullconversation-browser.js:373:5
set isActive chrome://chat/content/conversation-browser.js:373
switchingAwayFromPanel chrome://messenger/content/chat/chat-conversation.js:1452
connectedCallback chrome://messenger/content/chat/chat-imconv.js:80

which appears to be generated by chrome://chat/content/conversation-browser.js

this.docShell.isActive = value;

Comment 1

[Alessandro Castellani [:aleca]]

Thanks for reporting this.
Could you please write down the steps to reproduce this error? Which tabs you opened, which buttons you clicked, etc.

Pulling Kai in here as it might know better what's happening.

Comment 2

[vtol]

(In reply to Alessandro Castellani (:aleca) from comment #1)

Could you please write down the steps to reproduce this error? Which tabs you opened, which buttons you clicked, etc.

I am afraid that might be a difficult. Just stumbled upon it when looking into the console for another issue.

Just discovered another/different instance with the same underlying issue

TypeError: this.webNavigation is nullconversation-browser.js:283:5
get contentDocument chrome://chat/content/conversation-browser.js:283
removeUnreadRuler chrome://chat/content/conversation-browser.js:595
switchingAwayFromPanel chrome://messenger/content/chat/chat-conversation.js:1448

pointing to return this.webNavigation.document; in chrome://chat/content/conversation-browser.js

Comment 3

[Kai Engert [:KaiE:]]

That doesn't look like code that we touched recently for OTR.

The line quoted in comment 0 was originally added by Florian in March with bug 1534083, so let's ask him.

Comment 4

[vtol]

Attachment: conversation browser.js errors reproduced

Just had both error reproducing in a row

• upstream wan connectivity been terminated for a few minutes and then reestablished
• chat window been closed
• 2 IRC chat accounts (irc.freenode.net & irc.mozilla.org)
• with the changes in wan upstream connectivity the connections to the IRC nodes (logically) terminated and reestablished as well -> and with the latter probably the errors are showing.

Likely the errors are repdorucing

• after starting TB with (IRC) chat connectivity to remote nodes being established, and/or
• after prologned interuption of connectivity with remote (IRC) chat nodes when the connecticity is being restored

Comment 5

[vtol]

does not reproduce with Tb 69.0b2 (64-bit) en-GB

Comment 6

[Jorg K (CEST = GMT+2)]

Did you ever see this in TB 68 beta X? We'll be releasing TB 68 ESR soon, please recheck there.