I have personally reproduced the problem in Obsidian, while not being able to reproduce the problem on VSCode, the same for many others in this thread. This would heavily suggest that the errors are not the same.
I run KDE Plasma on Fedora (as well as Hyprland)
(If there is any other applications this would effect that I could test, lmk)
In the meantime I’m going to be using the command palette and the new tab icon. That works fine for me. Drag and drop would be better but whatever. I’m just shocked that this bug is 2 years old and the only thing that’s occurred so far is pointing the blame.
This may work for the shrinking audience of low DPI users, but it has already been confirmed by many users with modern monitor resolutions as being illegible.
I run high-DPI monitors with whole and fractional scaling, and have zero issues running Obsidian from the flatpak.
I’m not saying there isn’t a bug to be resolved, but I am saying that using the flatpak from the store is working perfectly as a workaround on Wayland.
That is not necessarily how bugs work, especially in Electron. Electron, especially Electron+Wayland constantly has reoccurring issues that occur in one app but not another, get fixed for some but not all users of an app, regress 2 years later … this is the nature of the Electron beast. People will point to Chromium working, but they often implement a lot of stuff independently of electron. People will point to other apps working, but that is usually luck of the draw on your system or a result of hard coded platform specific fixes, or cherry-picked git commits fixing it for at least some people in some conditions. A project with a tiny dev team like Obsidian cannot commit to using hand crafted electron versions or platform specific workarounds.
This bug does exist for some Linux VSCode users too - as much as people claim otherwise. It also doesn’t exist for some Linux Obsidian users. Sure, it seems to occur less in VSCode than Obsidian, but thats not really a reflection of a bug in Obsidian. Its a reflection of VSCode apply the typical electron partial fixes more quickly, or of just happening to hit whatever reproducibility requirements the bug has less often. Based on this being “fixed” before, its likely actually several bugs breaking the same feature.
I understand this ordeal is frustrating but well, Electron is frustrating. Unfortunately, its what we have.