Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)

A callback definitely seems like the way. 

Is there any value in having the clipboard item data ever be a Promise? In other words, rather than this:

```
typedef (Blob or DOMString) ClipboardItemValue;
callback ClipboardItemValueCallback = ClipboardItemValue ();
typedef Promise<(ClipboardItemValue or ClipboardItemValueCallback)> ClipboardItemData;
constructor(record<DOMString, ClipboardItemData> items);
```

I might expect this:

```
typedef (Blob or DOMString) ClipboardItemValue;
callback ClipboardItemValueCallback = (ClipboardItemValue or Promise<ClipboardItemValue>) ();
typedef (ClipboardItemValue or ClipboardItemValueCallback) ClipboardItemData;
constructor(record<DOMString, ClipboardItemData> items);
```

That signature lets the value be provided immediately, deferred, or deferred and resolved asynchronously.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/417#issuecomment-1483648182
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/editing/issues/417/1483648182@github.com>