[Feature Request] Improve log copying with auto-Markdown formatting and visual feedback

[eduardomozart]

Select Topic Area

Feature Request

Body

Is your feature request related to a problem? Please describe.

Currently, when users copy logs from the UI to report bugs on GitHub, the raw text often gets pasted directly into the issue. This creates massive walls of text that bloat the page, making issues difficult to read and scroll through. Additionally, when clicking the "Copy to clipboard" button, there is no visual indicator or feedback to confirm that the text was successfully copied.

Describe the solution you'd like

I would like to propose two quality-of-life improvements for the log copying functionality:

1. Auto-Wrap in Collapsible Markdown: When the user clicks "Copy", the clipboard payload should automatically wrap the raw log text in a collapsible HTML/Markdown block with a code fence (e.g., log). This ensures that when users paste the log into a GitHub issue, it is automatically formatted correctly and collapsed by default.
   Example output format:

<details>
<summary>Click to expand logs</summary>

```log
[2026-03-01 16:47:32.965]: Info: Sunshine version...
[2026-03-01 16:47:32.965]: Info: Package Publisher...

2. Visual Copy Feedback: Add a brief visual cue when the copy button is clicked (e.g., the clipboard icon turning into a checkmark for 2 seconds, or a small "Copied!" tooltip/toast). This provides necessary feedback to the user so they know the action was registered.

Additional context

• Example of a clean, collapsible log in practice: Sunshine Issue #4801
• Example of visual clipboard feedback: The DokuWiki copy2clipboard plugin demonstrates great, simple visual feedback when text is successfully added to the clipboard.
• Real-world implementation: The GLPI (Gestionnaire Libre de Parc Informatique) project already successfully offers both of these exact features - automatically wrapping copied text in collapsible Markdown and providing immediate, clear visual feedback to the user when copying.

[ReenigneArcher]

1. No, because I don't want to have to expand logs every time I view a bug report.
2. Sounds like a nice idea. I'll accept a PR for it.

[eduardomozart]

Number 2 implemented in LizardByte/Sunshine#4803