-
Notifications
You must be signed in to change notification settings - Fork 179
clipboardchange event feature #3345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
FWIW although this has been merged into a working draft, it's unclear how stable the feature is; looking at the git history it seems to have been part of a mass-merge in 2018, which I didn't investigate deeply, and looking at the issue tracker there are some issues like w3c/clipboard-apis#228 which could lead to design changes. So this seems like a case where we could use the process for early stage features. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you link to #3079 in a TODO so that we revisit this when we decide on something for early features?
…ures into clipboardchange
The
clipboardchange
event is a new feature that's now implemented in Chromium, although only available as an origin trial for now.Draft spec: https://w3c.github.io/clipboard-apis/#clipboard-event-clipboardchange
Chromestatus entry: https://chromestatus.com/feature/5085102657503232
Key advantage: avoid having to poll the clipboard to know if something has changed.