[dmsnell]

Resolves #3042
Resolves #2898

Summary

This 100% vibe-coded change addresses two frustrations with copying in the editor:

1. It’s not possible to copy content from a revision because clicking outside of the revision slider closes the history view.
2. Copying and pasting is rich-text unaware and only copies Markdown source as plaintext.

These changes fix the history viewer and require an explicit click to close (or a keypress of the Escape key, or by navigating to another note). This is a different behavior than the click-outside-to-close model, but it may be more ergonomic, because the old behavior prevents copying parts of an old version of a post.

Secondarily, several issues arose during the work on this feature relating to copy and paste behaviors. The app should be more aware of HTML/richly-formatted content when pasting, and will send two copies of copied content into the paste buffer: a text/plain version containing the markup source; and a text/html version containing the rendered note. This makes it possible for other applications to use the rendered content after copying.

A side-effect of this change is that it’s now possible to preserve basic formatting when pasting HTML content into the app, as it parses the inbound HTML, sanitizes it, and creates Markdown syntax from the HTML.

Before / After

These videos demonstrate both aspects of this change:

1. They attempt to select and copy a portion of an old revision of a note.
2. They copy a note’s content and then paste it into another app, showing how the copied content, even if copied from the Markdown source itself, retains its formatting through the copy.

As a note on this, most applications provide an alternative paste mode where it’s still possible to paste the plaintext content. In the After video, the plaintext content is automatically pasted into the search box since it doesn’t support rich content, but in something like an email, it would likely be possible with a combination like Cmd + Opt + V or “Paste without formatting.”

before-trunk-v2.mp4

after-feature-history-revision-copy-v2.mp4

[dmsnell]

I have performed checks on this and ran a (primitive, overly-naive) fuzzer on it to ensure that the changes aren’t introducing obvious flaws. My plan is to merge, try to deploy to staging, then deploy to production.