Unable to click some links in front matter properties

When navigating properties, some links are clickable and others are not.

Steps to reproduce

Assume the following note with front matter:

uid: 46b0e815-3078-45fc-9712-6bfb24813aef
source: https://obsidian.md
target: “[[Format Your Notes]]”
card: x-cardhop://show?id=contact:D63AAFB6-1EB1-4497-8CE0-B64781E9915B&contact=Creed%20Erickson%20III
from: drafts://open?uuid=95ACD9C7-7081-4E17-B5E0-28E1037A89C2

blah blah blah

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


Expected result

Expected all 4 linked sources to be opened.

Actual result

The “source:” and “target:” properties will open when clicked, the “card:” and “from:” properties will not. In this specific example, these are respectively a link to a contact card and a backlink to an originating source note in the Drafts application.


Attempting to follow the instruction above yields the following dialog:

A JavaScript error occurred in the main process

Uncaught Exception:

TypeError: Cannot read properties of undefined (reading ‘webContents’)

at a.click (/Users/creed/Library/Application Support/obsidian/obsidian-1.4.1.asar/main.js:6:4654)

at MenuItem.click (node:electron/js2c/browser_init:2:30394)

at a._executeCommand (node:electron/js2c/browser_init:2:35790)

Additional information

Mac mini (2018), 64GB Ram, Mac OS Ventura 13.5,
Obsidian Version 1.4.1 (Installer 1.3.5)
Drafts 39.2.1
CardHop Version 2.2.8 (1144.295.adf8f620a)

Problem with trying to get debug info resolved on system reset. Here’s the data:

Obsidian version: v1.4.1
Installer version: v1.3.5
Operating system: Darwin Kernel Version 22.6.0: Wed Jul 5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 22.6.0
Login status: logged in
Catalyst license: vip
Insider build toggle: on
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 0
Plugins enabled: 0


So from your text it seems Cardhop apparently uses the x-cardhop:// and Drafts the drafts:// URI and they are external programs. Normally with a browser these kinds of URIs need to be registered with a handler that can take care of them. Obsidian, by default, has one installed for the obsidian:// URI. So unless there are extensions that register these applications with URIs within Obsidian, this won’t work out of the box, as far as I know.

Fixed in 1.4.2

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.