iOS: Cursor disappears when editing table row after a certain length

Steps to reproduce

  1. Initialize a simple table.
  2. On any given row, start writing a long sentence, reaching about 230 line characters or more.

Expected result

We can still see the cursor blinking wherever it is that we’re writing.

Actual result

The cursor disappears, and it’s really hard to place it somewhere again.


Operating system: ios 16.3.1 (Apple iPad)
Obsidian version: 1.4.4 (99)
API version: v1.2.7
Login status: logged in
Catalyst license: none
Live preview: on
Legacy editor: off
Base theme: light
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 20
Plugins enabled: 18
1: Style Settings v1.0.3
2: Hider v1.2.4
3: QuickShare v1.3.1
4: Tag Summary v2.1.5
5: Smart Typography v1.0.18
6: Paste URL into selection v1.7.0
7: Emoji Shortcodes v2.2.0
8: Homepage v3.0.2
9: Map View v3.0.2
10: Advanced URI v1.35.0
11: Underline v1.2.1
12: Lumberjack :axe: :wood: v1.3.0
13: Chat View v1.6.0
14: Tag Wrangler v0.5.8
15: Periodic Notes v0.0.17
16: Trash Explorer v1.1.0
17: Calendar v1.5.10
18: Natural Language Dates v0.6.1

Additional information

While on this topic, it really doesn’t make for a nice experience the fact that on mobile table rows go on and on without line jumps. It makes it really hard to position the cursor where you want it and you find yourself constantly accidentally jumping back to the beginning.

My apologies - it seems I lost the environment section along the way, and edit is no longer available. Environment is the same as in this other bug I filed.

I copied over the environment info for you.

1 Like

does it happen in new vault?

It does. Here’s a screen recording taken in a clean env.

Note that this behavior is annoying on an iPad with a keyboard, but at least here I can navigate easily with the keys. On an iPhone it basically renders the “table editor” unusable, as you don’t know where your cursor is or how to put it somewhere else.

Still seems to be happening. Just having the issue right now.

Does this happen in source mode too?