iOS - Inaccurate Cursor Placement

[scuba-tech]

Environment

Joplin version: 10.1.0
Platform: iPhone XR
OS specifics: iOS 14.0.1

Steps to reproduce

1. Open large document (anything that requires scrolling in iOS)

2. Switch to edit mode

3. Attempt to place cursor anywhere beyond the first screenful of text

Description

When in edit-mode and attempting to place the cursor anywhere beyond the first “page” (anything where the text has been scrolled), upon tapping to place the cursor the document and cursor snaps back to near the top of the document.

When attempting to use a dragging motion to place the cursor (instead of tapping), the cursor instead snaps to the start or finish of the document.
At this point, editing appears to be disabled.

This bug has made editing documents greater than one page (as-viewed on iOS) effectively impossible.

Describe what you expected to happen

Being able to place the cursor anywhere within the document while in edit mode.

Original Forum Post

https://discourse.joplinapp.org/t/inaccurate-ios-cursor-placement/11269

Since ~10.0.53, in all larger notes when editing in the standard editor (not experimental), scrolling several pages past the current cursor position, and tapping, will jump the cursor position only a few lines from its previous position (jumping the scroll bar back), not where it should be. Happens intermittently with no current discernible pattern. Happens with any long file.

Another possibly related issue: if dragging the cursor itself (tapping and holding cursor, then dragging, that was introduced since iOS13), the cursor will jump to the start or end of the document, and cannot be moved anywhere else.

Logfile

(TBD, will edit and/or post separately)

[scuba-tech]

Logs

[bela53]

This also happens on Joplin Desktop, Linux/Ubuntu.

As described, Joplin snaps to the top of the page when editing any part in a large document like typing one letter (markdown mode). I cannot reproduce the issue consistently, it appears at some point in time. A current workaround is to restart Joplin to make editing possible (until the bug starts to happen again).

Note: bug seems to be introduced with the current version v1.1.4. Before it worked.

Update:
After more investigation, this snapping seems to occurs in combination with a previous search query.
If I type something in the search field (F6), select one of the found (large) notes and edit it, with each key press it snaps to the top.
If the same note is selected without having searched before, editing works as usual.

[scuba-tech]

I’ve just updated to Joplin iOS version 10.2.0, and just wanted to confirm that this bug behavior is still present.

Can’t scroll beyond the first viewport/window on note editing mode, unless I jump a paragraph or two at a time.

[scuba-tech]

Just updated to Joplin v. 10.2.1 (database v34), and can confirm that this issue still happens around half the time when trying to place the cursor.

When I tap to try and edit a different page/viewport, the editor snaps back up to near the top.
If I tap on the same page/viewport, it usually seems to work.

Video: https://imgur.com/a/6SJqnb4

---

UPDATE: I have discovered a workaround for now, if I scroll to where I want to cursor to be, and then press-and-hold on the screen for ~1 second, the cursor changes to a "drag-and-drop" mode with the blue cursor and a grey "shadow" cursor. When I release my finger, the cursor drops where I place it every time, and no longer snaps to nearby the previous location. I am placing this update here in the hopes that other iOS users see this when searching. Editing longer documents is still possible, it just currently requires to press-and-hold to move the cursor off the current page.

Video of workaround: https://imgur.com/a/BxCS4gQ

Hopefully this helps someone else out there. :)

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[scuba-tech]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

Yes, I checked my phone again to confirm: this issue is still present on iOS v. 14.2; Joplin v. 10.3.1

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[scuba-tech]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

Yes, I checked my phone again to confirm: this issue is still present on iOS

[StanyStany]

Hi everyone, I confirm too : this issue is still present (and annoying) on iOS.

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[scuba-tech]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

No idea, I gave up and have moved on to markdown via Textastic. Hopefully someone else here can confirm if this is still an issue.

[StanyStany]

Hopefully someone else here can confirm if this is still an issue.

It is.

[wishinghand]

It's an issue on my iPhone 12 Pro Max. Joplin version 10.7.2. It's not just scrolling down from the initial screen, but trying to place the cursor anywhere more than a page or so away from the cursor's current position.

[guiix-code]

Best illustrated with video (attached). Note I am tapping around line 40 each time.

Joplin.cursor.jump.iOS.14.4.iPhone.8.mp4

Environment

Joplin version: 10.7.2 (and previous versions for some time)
Platform: iOS 14.4 on iPhone 8
OS specifics: 14.4

Steps to reproduce

1. Create a new note with > 50 lines of text.
2. Edit and tap at start of list (or end of list).
3. Scroll down anywhere off screen, and tap again.

The cursor does not focus at the correct spot, but jumps a few lines from the original cursor position only.

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[wishinghand]

Still an issue for me.

[guiix-code]

Still an issue here too.

[StanyStany]

Still an issue indeed. It was such an annoyance that I had to move to Bear, sadly.

[scuba-tech]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

Still an issue for me. It’s bad enough that I gave up on Joplin for my org and moved to Textastic for my notes. (Still rooting for Joplin!)

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[StanyStany]

Fixed here ! Thank you very much, it's a real improvement, that may make me switch back to Joplin (iOS 14.5.1, Joplin 10.8.1).

[guiix-code]

Still an issue for me, unfortunately.

[StanyStany]

Still an issue for me, unfortunately.

Strange. What are your IOS and Joplin versions ?

[guiix-code]

iOS 14.6 on iPhone 8, Joplin 10.8.1

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[guiix-code]

Unfortunately, still an issue.

[StanyStany]

I can’t understand why it’s fixed for me and not for you, guys. We are probably using the same iOS and Joplin versions (iOS 14.6 and Joplin 12.1.2 here). Can it be related to our phones (iPhone 6s here, iPhone 8 for you, @doomsy) ? Can it be related to the fact that I now have a very few notes since I switched to another note taking app (2 notes now vs 1800 when I was using Joplin) ? That’s very strange.

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[guiix-code]

Still an issue.

Hopefully when the CodeMirror 6 update comes to iOS, the issue fixes itself.

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[guiix-code]

Still an issue.

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[guiix-code]

Using the beta editor does not have the problem. But the problem still exists in the old editor for what it's worth.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.