docs: add spec for clipboard rearchitecture #454
Conversation
This file contains 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
codebytere
force-pushed
the
add-clipboard-proposal
branch
from
1c8a6df to
b552fe5
Compare
ckerr
reviewed
Nov 3, 2021
zcbenz
reviewed
Nov 4, 2021
Co-authored-by: Charles Kerr <[email protected]>
5 tasks
codebytere
commented
Mar 3, 2022
5 tasks
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This document outlines a proposal for the future of the
clipboardmodule provided by Electron.Over the course of the last few months, Chromium has been making significant changes to their Clipboard API, including the ability to handle Custom Formats. Electron has had to break small aspects of its clipboard API to account for this, and it's unclear what other changes we may be forced to adapt to as they continue this work. Beyond this, users have been asking for an improved Clipboard API as well as surfaced a number of bugs with its current implementation - the most detailed of which is here. Given this, @jkleinsc and i have put together a more streamlined proposal for its future.