typora
Document page should not scroll upward without any apparent reason
Actual behavior
A text file with markdown content was created with Typora. Editing the same file in Typora.
I am switching apps back and forth: Typora to Web browser After manual editing and save of the Typora document; I go back to application from which I am transferring information; then switch back to Typora.
The page I had been on jump-scrolled up about a page upward toward the beginning of the document. It is a tap on a VIRTUAL page-up key.
Often this happens when trying to drag and drop a link. That is, selecting the URL in the browser's location field, then mousing down and dragging the URL to Typora... When hovering over Typora, the Typora app comes forward but document is "paged up" from spot where I previously left the document.
This erratic page up behavior also happens when editing the document as I am now in the Typora document.
As I was using Typora to compose the content of the Issue (before pasting into Github), the same erratic page up behavior also happens after a save.
Just now when I was editing this text, in Typora, the page jumped up one page-height. That is before my next save. I was typing.
I then proceeded to located my last edit to see if there was any data loss. I saw there was no data loss so sent command Cmd-S, to save. Immediately Typora jumped up a page again. So I had to scroll the document back to the bottom to resume editing.
Expected behavior Expected page not to move when dragging data over a Typora doc. Expected page not to move after saving Typora doc. Expected page not to move when editing Typora doc.
Plaform macOS 11.7.10 (20G1427)
My Typora document is saved in macOS Documents folder on an iCloud enabled Home directory.
Pure Vanilla macOS in terms of system extensions and we can include Finder application as System. No special extensions on Finder, or macOS.
Plain Vanilla Typora Version 1.9.4 (7260) No additions/themes, nada.
Thank you Love your work. Love the app. This behavior described here has been present for me since at least 1.7 or 1.8. For a year, maybe longer. I did not report it previously because I assumed it was such a prevalent thing somebody would report it before me and it would be fixed in this recent 1.9; which was a very anticipated release for me.
