You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 15, 2022. It is now read-only.
scrolling is not fluid on iOS 14.4.2, with SN 3.6.6 and the Markdown Basic Editor.
In edit mode, if the keyboard is visible and the note is long (more than 2-3 screens), scrolling gets stuck: can scroll in fluid motion to top or bottom; need to place the cursor somewhere (up or down, depending) and then repeat scroll movement
This may be related to the fact that I see two scroll bars:
one for the note: ie the top header (edit/split/preview) stays in place while text scrolls
Another one outside of the first one where the header is also scrolled out of the screen: only when this second one is activated can I get to the bottom of the note (and then it’s the reverse problem going up)
So effectively I need to scroll through two areas to move about
EDIT: Also seems to happen on markdown-pro. Plain editor works fine as expected
thanks
The text was updated successfully, but these errors were encountered:
Hi @affvalente, thanks for bringing this issue to our attention! I was able to reproduce this bug on iOS but not on Android. I'll discuss this further with the dev team and will reach out to you when a fix is available to test.
Hi -
scrolling is not fluid on iOS 14.4.2, with SN 3.6.6 and the Markdown Basic Editor.
In edit mode, if the keyboard is visible and the note is long (more than 2-3 screens), scrolling gets stuck: can scroll in fluid motion to top or bottom; need to place the cursor somewhere (up or down, depending) and then repeat scroll movement
This may be related to the fact that I see two scroll bars:
So effectively I need to scroll through two areas to move about
EDIT: Also seems to happen on markdown-pro. Plain editor works fine as expected
thanks
The text was updated successfully, but these errors were encountered: