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

@fergald I have the same concern and I think it's an important detail to work out before proceeding with the API. At least for Chromium we cap the duration of `beforeunload` handlers because we don't want tab shutdown to be slow. Also I don't think `onbeforeunload` handlers are allowed to specify custom text.

@rakina sure, in a world where navigating away eagerly fetched the clipboard contents, we could do that whether or not the page was going into bfcache. I thought you were suggesting that we wouldn't need to grab the data because the page might come back. If developers are worried about snappy navigations they probably won't use this API regardless, since this proposed work-on-shutdown model is going to be slow one way or another.

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

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