Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240)

annevk left a comment (w3c/clipboard-apis#240)

To handle that use case in Safari you'd have to eagerly fetch all the types you are interested in. I think that is a better model as only the websites that care about holding that much data in memory will end up paying for it.

Snapshotting the entire entry for each call to `read()` is really rather wasteful. As you've also realized per this issue. Since we have an opportunity to move away from it without any API change or opt-in from web developers (which as pointed out will likely not bother opting in unless they have large teams and the proper incentives), I think we should take it for the benefit of end users.

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

Message ID: <w3c/clipboard-apis/issues/240/3280161427@github.com>