#222: Request review of (text only) Async Clipboard API
Discussions
2018-04-24
Travis: I looked at this this AM. We have filed our issues on their repo — same editor as the keyboard map API. Not sure we've heard back. I commented on a few issues. In Tokyo we discussed — is it enough to gate this clipboard access on a user gesture? We have semantic events in the platform for when the user wants to perform a copy or paste. We can map the gesture to that event.
Kenneth: If you are online in google docs, you'll have it in the menu (like "paste content"). Helpful
Alex: In Tokyo, we wanted to see language on user gestures. the language around semantics is hard, becasue you delegate your UI
...I'd love to see security and privacy section in the doc, and non-normative notes for implementations.
Dan: do they not have an issue on this?
...On both this and the keyboard map issue, we don't have specific links from our issue to the issue that we're interested in. I'm happy to do that legwork.
Travis: We could track their issue 52, on user gestures.
OpenedJan 5, 2018
Hello TAG!
I'm requesting a TAG review of:
navigator.clipboard
,readText()
andwriteText()
)Further details (optional):
You should also know that...
This review is only for the text parts of the API since we are still in the process of designing the portions of the API that add clipboard support for images and delayed content generation.
We'd prefer the TAG provide feedback as (please select one):