Context menu doesn't work on a plugin description page

Bug reports
1

Steps to reproduce

Go to: Options → Community Plugins → Browse → open any plugin page
Try to do some actions that require the context menu: copy a link, image or run a plugin-specific action.

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

Y

Expected result

The context menu with actions appears

Actual result

You can only copy a selected text through the menu

Environment

SYSTEM INFO:
Obsidian version: v1.6.5
Installer version: v1.4.13
Operating system: Windows 10 Pro 10.0.19045
Login status: not logged in
Insider build toggle: off
Live preview: off
Base theme: light
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 23
Plugins enabled: 0

Additional information

I think a limited functionality here is intended but I find very inconvenient that I need to search something in an external browser just to copy what’s already opened in Obsidian

2

Context menu does work however you can only copy link names. Images can be copied by inline selecting them and pressing ⌘C.

Inline selection of pictures:

  1. place cursor outside and next to the picture on the left
  2. drag and hold left click and move the cursor horizontally to the right
  3. release left click after you see your image selected

You can also drag & drop content from the plugin page—including links and pictures—but I think this functionality is rarely useful.

What you are suggesting is actually two new features:

  1. copy link context menu action in plugin pages
  2. copy image context menu action in plugin pages
3

Rarely but useful. I always find myself trying to review some link. I could’ve open them inside of Obsidian using Surfing plugin, but I can’t. Otherwise I need to use an external browser but not the default one, but I can’t. Searching by the text content is very inconvenient.

Anyway, thank you for workaround with drag’n’drop. Thought it’s still a workaround.

I believe that overall proposal is not to add copying features but to relax limitations in settings UI. They really have no sense, because some windows are windows but the others (like plugin descriptions) are actually pages and I want to have a corresponding functionality