Can't inspect elements in v1.11 dev tools

Steps to reproduce

  1. Open a note in desktop Obsidian 1.11.
  2. Press Ctrl+Shift+I to open dev tools.
  3. Click on the inspect button, then click on an element inside a note.

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

Reproduced in sandbox.

Expected result

For the inspect function to select the element and show it in its expanded HTML code context, as usual.

Actual result

While hovering the element, it is correctly shown in its code context, but once the user clicks, the whole note is highlighted with blue, and the HTML code view jumps back to the top level, collapsed state.

I can’t always reproduce it, might have something to do with switching between multiple notes before the bug occurs. In my actual vault the code shown after clicking are sometimes parts of a note open in the background, not the active one.

Environment

SYSTEM INFO:
Obsidian version: v1.11.4
Installer version: v1.11.4
Operating system: Windows 10 Enterprise 10.0.19045
Login status: not logged in
Language: en-GB
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 0
Plugins enabled: 0

RECOMMENDATIONS:
none


Additional information

when hovered:

when clicked:

this is a chrome/electron problem and we can’t do anything about it.

If I roll back to a previous installer version would that solve it, or do all Obsidian 1.11 versions, regardless of installer version, have this issue?

The issue is in the installer version, not the Obsidian version.

You can install the 1.10.6 installer (no issues with the element inspector) then download 1.11.4 and future updates in-app for the time being.

Thank you for saving my sanity :smiley:

Indeed. I’ve done the same. It was quite frustrating for the element picker to work twice, not work five times (or whatever), and then work again.

According to a web search, the chromium folks are aware of the regression, so we just have to wait a bit for the fix to filter down.

In Obsidian 1.11, the inspect tool highlights the whole note instead of the element when multiple notes are open. Open only one note at a time or restart Obsidian before inspecting. Report this with steps to help the devs fix it.

Could you link to the Chromium issue so we can track it? Thanks.

Does downloading and installing 1.11.7 fix this problem?

We can’t reproduce anymore.

Also which OS are you running?

Unfortunately it’s still happening on macOS for me. This is using the public 1.11.7 installer downloaded from obsidian.md.

SYSTEM INFO:
	Obsidian version: 1.12.1
	Installer version: 1.11.7
	Operating system: Darwin Kernel Version 24.6.0: Wed Nov  5

I can test on Windows tomorrow.

thank you, I don’t know why some people can repro and others can’t

As mentioned earlier, it’s inconsistent. I played around on macOS a bit more yesterday and the picker started working for a while and then randomly stopped again (showing the blue overlay and the Elements tab not jumping to the section).


That said, it seems to be alright in Windows with ~5 minutes of clicking around.

update: It’s still happening on Windows as well.

Obsidian_bsQIguLdfA

SYSTEM INFO:
	Obsidian version: 1.12.1
	Installer version: 1.11.7
	Operating system: Windows 11 Pro 10.0.26200

Does anyone know if this has been fixed in Obsidian v1.12.7 with the Electron update to v39.8.3?

I can’t find the Chromium issue where this was tracked.

FWIW: I’m still running into it on Mac (in the sandbox vault) but it’s quite inconsistent :woman_shrugging:
(I really have no idea what triggers it and what seems to “fix” it, even temporarily)

SYSTEM INFO:
	Obsidian version: 1.12.7
	Installer version: 1.12.7
	Operating system: Darwin Kernel Version 24.6.0: Mon Jan 19 21:56:28 PST 2026; root:xnu-11417.140.69.708.3~1/RELEASE_ARM64_T6020 24.6.0

Same today on Version 1.12.4 installer 1.12.4 Any news?

I have the same issue with version 1.12.7, using macOS Tahoe 26.4.1.

As a workaround, I found that the accessibility mode keeps the element selected with the inspector. To enable it, there is a button at the top right of the DOM tree view called “Switch to Accessibility Tree View.” When I inspect an element in this mode, the element keeps selected.

I know this is not ideal, but I hope that a proper fix will be available soon.

Thanks for the tip. I’ll give it a try.

Fingers crossed the next installer/Electron update sorts it out.

It feels like when I’m just noodling around it works fine, but when I actually want to do a quick check of something to help out or work on something for myself, it flakes out. lol :upside_down_face:

Yeah… you say it.

I’m wondering why nobody else found out that a simple click on the accessibility button is THE workaround to use.