Operating system
Windows
Joplin version
3.4.5
Desktop version info
Joplin 3.4.5 (prod, win32)
Device: win32, AMD Ryzen 7 5800X3D 8-Core Processor
Client ID: a6138bdeb3ec4952ac6c263eeb9fb657
Sync Version: 3
Profile Version: 48
Keychain Supported: Yes
Alternative instance ID: -
Revision: a5d37a0
Backup: 1.4.3
Sync target
S3
Editor
Markdown Editor
What issue do you have?
Not sure if this is a bug or something on my end- for some reason it only happens on one of my devices
When I right click on a link (external URL, or markdown image embed) in the markdown editor, I don't get the normal context menu options (Screenshot 2025-08-17 150014).
This happens in both my joplin profiles on this device (I have a work profile and a personal profile).
If I open the joplin dev instance on the same device ("C:\Program Files\Joplin\Joplin.exe" --env dev), I get the expected context menu options (Screenshot 2025-08-17 150413.png).
I tried disabling all plugins (except for the built in backup plugin) in my normal profiles, but it didn't change the behavior.
On my other device, it works as expected in my normal profiles. Both devices are running Windows 11 and joplin 3.4.5.
Screenshots
the issue also happens on a third device- this one only has a single profile (the default one) so seems unrelated to multiple profiles
So I have three devices:
Personal laptop - Windows 11 24H2 - Joplin 3.4.5 - Context menu shows expected options when right clicking on links or markdown image embeds
Desktop PC - Windows 11 24H2 - Joplin 3.4.5 - Context menu doesn't show any of the normal options when right clicking on links or markdown image embeds
Work Laptop - Windows 11 24H2 - Joplin 3.4.5 - Context menu doesn't show any of the normal options when right clicking on links or markdown image embeds
I don't see what could be different about the other two machines that's causing different behavior. Disabling all 3rd party plugins makes no difference, but if I open the dev instance it works as expected 
Any error in the log or console? https://joplinapp.org/debugging
This is the debug output that I get immediately after right clicking a link (https URL) or markdown image embed:
Logger.ts:317 12:35:49: PluginRunner: Got message (3): joplin.commands.execute editor.execCommand {name: 'getItemsUnderCursor'}
Logger.ts:317 12:35:49: CommandService::execute: editor.execCommand {name: 'getItemsUnderCursor'}
Logger.ts:317 12:35:49: CodeMirror6: execCommand {name: 'editor.execCommand', value: {…}}
Logger.ts:317 12:35:49: PluginRunner: Got message (3): joplin.commands.execute selectedText
Logger.ts:317 12:35:49: CommandService::execute: selectedText
Logger.ts:317 12:35:49: CodeMirror6: execCommand {name: 'selectedText', value: undefined}
however, it appears that I get the exact same output on the machine where it's working:
Logger.ts:317 12:54:20: PluginRunner: Got message (3): joplin.commands.execute editor.execCommand {name: 'getItemsUnderCursor'}
Logger.ts:317 12:54:20: CommandService::execute: editor.execCommand {name: 'getItemsUnderCursor'}
Logger.ts:317 12:54:20: CodeMirror6: execCommand {name: 'editor.execCommand', value: {…}}
Logger.ts:317 12:54:20: PluginRunner: Got message (3): joplin.commands.execute selectedText
Logger.ts:317 12:54:20: CommandService::execute: selectedText
Logger.ts:317 12:54:20: CodeMirror6: execCommand {name: 'selectedText', value: undefined}
It's definitely the same Joplin version on all devices? Because one of the recent changes could affect the Markdown editor and the right-click menu in particular. Do you use the Rich Mardown plugin?
doh you nailed it, it's rich markdown!
I completely forgot that these context menu options were provided by rich markdown (not native to joplin) 
I was able to isolate the difference with the rich markdown behavior on the machines in question:
The context menu options only appear when "follow note links with ctrl" is enabled in rich markdown's settings. I had disabled that setting, since Joplin 3.4.x had added that feature (following links with ctrl + click) natively. The other machine still had that setting enabled
Not sure if that's intended behavior or a bug, but I'll report that against rich markdown. Sorry for the confusion!
Rich Markdown works fine, it's mostly because we've integrated some features from it to the main app that conflicts are appearing (for example the app would also duplicate inline images if the relevant Rich Markdown option is enabled). We probably need to decide what to do before the final release - perhaps disable Rich Markdown by default, but I'm not entirely sure what features would be missing if we do this
1 Like
FWIW the main feature I use from rich markdown is displaying <img> formatted images in the markdown viewer editor (since the new image rendering option doesn't do that, it only displays standard markdown image embeds)
1 Like
