Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161)

Thanks for the feedback.

> In our case we just need to read a blob. Usually it will take a negligible amount of time. However since reading a blob is async it means once the result is available, a following clipboard call is not synchronously inside a user gesture event. In Chrome this is not a problem as the user activation rules allow a short timeout. In other browsers that do not implement these user activation rules, it's a problem, but that problem can be solved by implementing Chrome's user activation rules.

According to https://bugs.webkit.org/show_bug.cgi?id=222262#c3 there's a workaround not requiring a different user activation API. In order to solve the reporter's issue, it seems reasonable to not extend the scope to different user activation APIs, unless required.



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