Whenever I go into a RemNote page and I try to scroll down, then it scrolls up on its own. When I use the split screen, usually only one of the two pages have this problem ( specifically the one that I opened last, while the other one is fine). I find this issue both in the desktop app and in the browser.
Update: besides, I tried to downgrade the desktop app to the version 1.2.9 and I noticed that this problem doesn’t come up (while in the browser the issue is still there). Subsequently as a counter-proof, I tried to upgrade the desktop app again to the 1.3.4 version and unfortunately, the issue still persists.
yes the same problems happened in 1.3.4 ver of desktop
I try to scroll down, then it scrolls up on its own
Yeah, I’ve encountered the same problem. I hope they can fix it soon
It happens when you have text cursor in the document’s title.
+1 Same problem here
turn off setting - interface - sticky header
Thank you! This helped me to solve this problem. So, it is a sticky header bug.
Thanks for highlighting this. Found this corresponding GitHub Bug Report.
Can anyone replicate this multiple panes behaviour?
Moritz @ GitHub: Do you notice any pattern among the documents where this happens?
Also, does deactivating the Sticky Header, like @YOUNG_LEE suggested, eliminate this issue for you?
Or are you experiencing this bug even without Sticky Header enabled (before or after noticing it) and/or your cursor not in the document title?
Thanks in advance! The devs. are aware of the issue, but it would be very helpful to get more details regarding the behaviour of this bug.
Yes, by deactivating the Sticky Header, this issue is eliminated. Moreover, even if I have the Sticky Header enabled and I click somewhere else which is not the document title, this also solves the problem temporarily (so it doesn’t come up until I open another page and I have the cursor again in the document title).
In conclusion, this issue occured only when I had the Sticky Header enabled, plus my cursor is in the document title.
Thanks for the report! This will be fixed in the upcoming mini update. Kindly wait for 1.3.6, and PM if the bug isn’t fixed for you.