-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No longer functional on TB 115.3.0 (64-bit) on Windows #10
Comments
I cannot reproduce this issue on 115.3.0 Which shortcuts exactly can you reproduce this problem with? Have you tried assigning other shortcuts? Are you 100% certain the shortcuts used are not already taken by Thunderbird features? |
Hi again. Thanks for the prompt response. A few things:
The debugger was definitely showing no The shortcuts worked fine when opening a message in a separate window/tab (e.g., by double clicking a message in the messages list). STR:
Thanks! |
Can you reproduce the issue with a fresh Thunderbird profile? Do you have any other plugins installed which could interfere? |
I can reproduce this issue on TB 115.3.1 and 115.3.2 64bit Windows. In dev console I see:
No ID. |
I had the same exact symptoms as @vizustom did. I also had no other plugins installed. I will try to do a fresh install of Thunderbird this weekend on a new Win 11 Pro user account and see what happens, and report back. |
I am having the same issue, and the same JS console:
|
lispengineer said
i will also note that the shortcut works for me if i have the message showing in a preview pane (which i don't always have toggled on.) it's only in the message list without the preview pane open that it fails. |
Hi there,
This wonderful extension is no longer functioning for me on TB 115.3.0 (64-bit) on Windows.
I looked into the code, and it appears that this part results in an array of zero messages:
It doesn't fail the
!messages
check as it seems to be a zero-length array.I do not know if something has changed or my Thunderbird installation is broken.
Let me know if I can help fix this somehow.
Thanks!
The text was updated successfully, but these errors were encountered: