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

@johanneswilm I think this is actually from the 2023-**02**-09 call.

> 2023-01-09 call:
> 
> > anasollanokim (Microsoft): presented delayed clipboard rendering last time, resolving feedback: does existing API work?
> > anasollanokim: been working on that but no resolution yet, since we're unsure how the promises are going to be resolved
> > anasollanokim: can't guarantee when the promise will be resolved browser-side
> > anupam (Microsoft): need signal that system is trying to read data, exposed to web
> > whsieh (Apple): that's when promise is called
> > text/html => promise1
> > image/png => promise2
> > promise2.when()
> > johanneswilm: what to do when navigating away?
> > johanneswilm: when you navigate away, the promise is gone
> > whsieh: (or the promises are all resolved — there are multiple ways to solve this problem)
> > anupam: We will work with our partners and see if the promise approach works for them. If not, then we can discuss further.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/417#issuecomment-1452768862

You are receiving this because you are subscribed to this thread.

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