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

> > Yes, because we want to allow sites to construct the data asynchronously, but eagerly.
> 
> Right, that makes sense. Four options, then:
> 
> * Eager: a `DOMString` or `Blob`
> * Eager, but asynchronous: a `Promise` of a `DOMString` or `Blob`
> * Deferred: a callback returning a `DOMString` or `Blob`
> * Deferred, but asynchronous: a callback returning a `Promise` of a `DOMString` or `Blob`

Are these suggested alternative ctor param types? If so, they can't be or'd because of the promise. But I agree with the premise they could all be useful.

I agree it would be nicer not to have to wrap your argument with `Promise.resolve()` but it also doesn't seem too awful, and it's what the API was launched with, presumably because of the Promise union problem.

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

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