List property elements can no longer be opened with Ctrl-Enter

Steps to reproduce

Create a note and give it a list-type property.
Add a link to the list.
Highlight it by running Add File Property, hitting Esc twice, using the arrow keys to navigate to the list, hitting Enter, and using Shift-Tab to highlight the link. Hit Ctrl-Enter.

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

Yes; reproducible in the appimage and in a sandbox Vault.

Expected result

The link opens.

Actual result

The link is not opened.

Environment

SYSTEM INFO:
Obsidian version: v1.11.7
Installer version: v1.10.3
Operating system: #1-NixOS SMP PREEMPT_DYNAMIC Thu Dec 18 12:55:23 UTC 2025 6.12.63
Login status: logged in
Language: en
Catalyst license: none
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

The cause is that Ctrl-Enter is trying to open a link under where the cursor was in the body despite the fact that the list element is tab-highlighted. To reproduce this, create a new note with a list property, add a link as one of its elements, make the body of the note contain only a link, move the cursor over the link, navigate to and highlight the link in the property via the method described in the reproduction section, and hit Ctrl-Enter. The link in the body, not the link in the property, will open.

Alt-Enter doesn’t work as expected, either.

I can’t reproduce this.

So you’re getting the expected behavior? Interesting

I created a new user account and got the expected behavior there. I have no idea why a sandbox Vault would be insufficiently isolated to reproduce the behavior. I’m going to try removing a few things and will report back.

The culprit file was obsidian-1.11.7.asar. Deleting it and letting it regenerate has fixed the issue with no noticeable side effects.

The issue has re-appeared. Doing more testing.

It seems that deleting the file is a temporary fix. Closing and re-opening the app brings the issue back, even with restricted mode enabled, which means that plugins are not the source of the issue.

Deleting the file is a temporary fix, because you have automatic updates enabled and the file is download again as the app updates itself.

I can reproduce the bug now, however it doesn’t happen all time and I am not quite sure what triggers it.

We will fix a related issue in 1.13. eta unknown.
Let me know if your problem is fixed too.