Fix message copy in the Electron shell - #22
Open
SuperstructureJH wants to merge 1 commit into
Open
Conversation
SuperstructureJH
marked this pull request as ready for review
August 14, 2026 08:59
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
clipboard-sanitized-writepermission only for the trusted loopback Harness main frameRoot cause
The Harness message action already calls
navigator.clipboard.writeText, but the desktop shell rejected every permission request. Electron therefore denied clipboard writes inside DSH Desktop even though the same UI worked in a normal browser deployment.Verification
npm test— 7 test files, 37 tests passednpm run typechecknpm run buildAcceptance boundary
Automated tests, type checking, and the production build pass. A real message-copy click in the packaged desktop app still needs manual acceptance.