Ghost-scrolling through menus (react bug?)

Operating system

Linux

Joplin version

3.4.12

Desktop version info

Joplin 3.4.12 (prod, linux)

Device: linux, AMD Ryzen 7 8845HS w/ Radeon 780M Graphics
Client ID: 9959465eea794e60b1b95760c308ca91
Sync Version: 3
Profile Version: 48
Keychain Supported: No
Alternative instance ID: -

Revision: e9a9f68

Backup: 1.4.3
Combine notes: 1.2.2
Conflict Resolution: 1.2.3
Diff view: 0.2.0
Extra Markdown editor settings: 1.11.0
Favorites: 1.3.2
Freehand Drawing: 3.1.0
History Panel: 1.0.4
Hotfolder: 1.2.2
Import local CSS: 1.1.0
Inline tags: 1.3.0
Inline TODO: 1.9.0
Kminder Mindmap: 0.8.7
Note list (Preview): 1.1.0
Note list and sidebar toggle buttons: 1.0.3
Note Rename: 1.0.0
Note Tabs: 1.4.0
Persistent Editor Layout: 2.2.0
Quick Links: 1.3.2
Resume Note: 0.4.0
Save Note as MD: 1.0.2
Space Indenter: 0.2.6
Table Formatter Plugin: 1.2.1
Tagging: 1.0.3
Templates: 2.4.0
Whitespacer: 1.0.2
YesYouKan: 1.1.2

Sync target

Joplin Cloud

Editor

Markdown Editor

What issue do you have?

Often if I switch away from Joplin (desktop) and then come back, I will see the cursor, if a menu is a focus, endlessly scrolling in what looks like right to left, like I am holding down the left-arrow key. It stops if I type anything. Or I click on the notebook hierarchy and they all collapse. (That’s what happens if you hold down the left-arrow key.)

I have seen the behavior on my desktop and my laptop.

I'm running Joplin on Fedora Linux 43 on both machines (installed via an RPM that wraps the AppImage). I see this happening with Discord as well (also uses react and Electron, I believe). So, I’m guessing the bug has to be somewhere not in Joplin.

I am posting this here because I am wonder if anyone else has seen this behavior. Again, I have only seen it if I changed workspaces and then switched back.

Has anyone else heard of or experienced such a behavior?

I did an update to the OS today and the problem seems to have disappeared. I suppose it is worth knowing that something like this has been witnessed. We’ll see if the corrected behavior holds or not and then I will come and mark this as solved.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.