Bug: Failure to update message pane when a different message is selected in message list pane.
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2021-09-23 21:49:44+00:00
Resolved: 2024-02-20 01:09:48+00:00

Environment: Windows 10 Pro 64-bit
TB 78.14.0 (32-bit)

I am reporting a strange display update failure I observed this morning for a while (it went away after I chose a different folder and came back to the original folder).

Symptom. No update of message pane when I choose different message summary line (in message summary pane).

I was looking at the latest message shown at the bottom of message summary pane. The message body was shown in the message pane.
When I moved up on the message summary pane, i.e., click on the message above the original, the message pane was not updated.
It continued to show the last one.

Puzzled, I clicked a few of the message summary lines, still no update of message pane.
I even used the cursor key to move up and down the message summary lines. Still no update of message pane.
I could not read other messages at all.

What should happen.: the message pane ought to be updated to show the message selected.

Well, after I switched to a different folder and came back, the update started to work.
I could select the summary line to show the desired message pane.

The problem occurred out of blue. I could not reproduce it.
All I can think of is that I was opening some links in a message in a browser (Firefox) and then came back to the message and tried to read a message earlier than that. But a few attempts could not reproduce the issue.


I opened the error console, and I *think* these two messages may be related to the symptom I observed.
```
06:20:04.683 Error: We do not implement timed selection. JsTreeSelection.jsm:149:11
    timedSelect resource:///modules/JsTreeSelection.jsm:149
    _moveByOffset chrome://global/content/elements/tree.js:1422
    setupEventListeners chrome://global/content/elements/tree.js:931
```
I don't know if my symptom I observed this morning for a while (it went away after I chose a different folder and reverted to the original folder) falls within this bugzilla.

The other message, uncaught exception, is rather lengthy (200+ lines) if I unfold it completely and so I am uploading it as attachment.

The shorter folded message is shown below.
```
06:20:04.683 Uncaught 
Exception { name: "NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS", message: "[JavaScript Error: \"We do not implement timed selection.\" {file: \"resource:///modules/JsTreeSelection.jsm\" line: 149}]'[JavaScript Error: \"We do not implement timed selection.\" {file: \"resource:///modules/JsTreeSelection.jsm\" line: 149}]' when calling method: [nsITreeSelection::timedSelect]", result: 2153185313, filename: "chrome://global/content/elements/tree.js", lineNumber: 1422, columnNumber: 0, data: XPCWrappedNative_NoHelper, stack: "_moveByOffset@chrome://global/content/elements/tree.js:1422:29\nsetupEventListeners/<@chrome://global/content/elements/tree.js:931:20\n", location: XPCWrappedNative_NoHelper }
tree.js:1422
```

Unfortunately, I think the "copy" function from an object in debug console does not seem to be complete. Correct me if I am wrong.
But what I copied in the attachment does not seem to reflect what is visible in debug console completely. I will upload what I see in debug console in the next attachment.