Cursor disappears when switching to source mode in a table

Bug reports
, , ,
1

Steps to reproduce

  1. Open sandbox
  2. Insert table
  3. Switch to source mode
  4. The cursor is gone
  5. Switch source mode off
  6. The cursor is back

Did you follow the troubleshooting guide? [Y/N]

Y

Expected result

The cursor should not disappear when switching to source mode.

Actual result

The cursor disappears.

Environment

SYSTEM INFO:
	Obsidian version: v1.8.7
	Installer version: v1.8.4
	Operating system: Darwin Kernel Version 24.3.0: Thu Jan  2 20:23:36 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T8112 24.3.0
	Login status: not logged in
	Language: en
	Insider build toggle: off
	Live preview: on
	Base theme: adapt to system
	Community theme: none
	Snippets enabled: 0
	Restricted mode: on

RECOMMENDATIONS:
	none

Additional information

2 Likes
2

@WhiteNoise you were super helpful with my last bug report, so I just wanted to ping you and see if you have any luck reproducing this issue.

Also, I forgot to add tags to the bug report when I created the issue at first, but is there a way for me to add them retroactively?

Thanks in advance.

3

Please don’t ping/tag team members (or moderators) in a topic if you haven’t talked before.

The team looks at every report. Have patience. Thanks.

1 Like
4

My apologies, I’ll avoid that moving forward.

Regarding the tags, is there a way to add them to an existing topic? I’m not too familiar with this forum technology so I’m not sure if I can do that on my end.

Also, let me know if you need more details to reproduce the issue on your end. I am happy to record and post a screen recording.

5

thanks

1 Like
6

Hello, dropping by to say I have this issue as well.

I’m using vim mode + japanese keyboard

I think this is part of the same issue:

If I’m in live preview mode and my cursor is in a table, when I open a different note (ex via ctrl+o), my cursor disappears and I have to click with my mouse to get it back

1 Like
7

I’m having this issue as well these days. Actually thought it was from recently updating Obsidian (1.11.4) last week, since I don’t remember experiencing this bug over the last year.