[w3ctag/design-reviews] TAG review: Async Clipboard - image/delayed content (#350)

Góðan TAG !

I'm requesting a TAG review of:

  - Name: Async Clipboard - image/delayed content generation
  - Specification URL: https://w3c.github.io/clipboard-apis/#async-clipboard-api

  - Explainer, Requirements Doc, or Example code:
    * [original explainer](https://github.com/garykac/clipboard/blob/master/clipboard.md) - with background info about Async clipboard in general. Note that this has obsolete references to `DataTransfer`.
    * [read/write explainer](https://docs.google.com/document/d/1lpi3-9vBP_1b7hZc2xBs0s_HaACJ6UigZZqHlJSNeJg/edit#) - describing just the new parts that we're trying to add
    *  [jsfiddle](https://jsfiddle.net/c4xm6jdy/21/) -  with mock implemenation
  - Tests: https://github.com/web-platform-tests/wpt/tree/master/clipboard-apis (although note that these are still being updated)
  - Primary contacts: garykac

Further details (optional):

  - Relevant time constraints or deadlines: Currently working on implementation in Chrome
  - [x] I have read and filled out the [Self-Review Questionnare on Security and Privacy](https://www.w3.org/TR/security-privacy-questionnaire/). The [assessment is here](https://github.com/w3c/clipboard-apis/blob/master/tag-security-privacy2.md).
  - [x] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/)

You should also know that...

* The Clipboard API spec is large and describes the old "Event API" and the newer "Async API". For this TAG review, we're interested in feedback on the `read()` and `write()` methods of the new Async API (although comments on other parts are welcome).
* We did a previous TAG review for the Text-only portion of the Async API. That TAG review is [here](https://github.com/w3ctag/design-reviews/issues/222).
* At this point, we're primarily interested in making sure that the shape of the read/write API looks good so that we can write more detailed descriptions.
* For the previous TAG review, I called in on the review meeting so that I could answer questions directly. Let me know if you'd like to do that again.

We'd prefer the TAG provide feedback as (please select one):

  - [x] open issues in our Github repo for each point of feedback
  - [ ] open a single issue in our Github repo for the entire review
  - [ ] leave review feedback as a comment in this issue and @-notify [github usernames]

--------------------------

_Please preview the issue and check that the links work before submitting_

For background, see our [explanation of how to write a good explainer](https://w3ctag.github.io/explainers).


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/350