New notes are repeated

[tryonkus]

When I create new sidenotes, they are sometimes repeated.

• The sidenotes appear to be identical.

• If I export to markdown, they have the same hash/index.

• If I delete one copy of the note, the other is unaffected.

• This behavior continues if I perform an Obsidian restart and if I quit the app and restart.

• When this behavior occurs, it occurs consistently across different Obsidian notes.

• I am generally applying sidenotes to selections that are 15+ characters.

• I tried applying a note to the word "from", and while the plugin lost the connection to the anchor text, it created two identical notes.

• I have only seen this on the Mac version and not on my iPad.

• I've also seen the plugin work as expected but haven't been able to determine what triggers the change.

• macOS Tahoe 26.2

• Obsidian version 1.11.5 (Installer 1.8.4)

[tryonkus]

Update:

• I discovered today that if I complete a comment with control-enter or command-enter on my MacBook, then only one copy of the comment is created. If I click on the Add button, then two copies of the comment are created.
• If I update a comment and close with command-enter, then the comment updates normally.
• If I update a comment and close by clicking on Save, I see two messages saying the comment has been updated, but only one update occurs, even if there were originally two comments generated.

It appears both the Add and Save buttons are causing double executions, but in the case of Update, those both are performed on the same comment.

[mofukuru]

Thanks for the detailed report! This should be fixed in the latest version — the root cause was the Add/Save buttons firing twice due to duplicate event handlers. Give it a try and let me know if you're still seeing it.

[tryonkus]

the root cause was the Add/Save buttons firing twice due to duplicate event handlers

I had guessed it was something like that, since it didn't happen when I closed with control-enter. FWIW, I work in IT, and while I'm not a software tester, I'm good at breaking stuff.

Thanks for fixing this—I will try to check the updated plugin this afternoon (US Eastern time).