Re: [w3ctag/design-reviews] Raw Clipboard Access API (#406)

The writing-native-exploit-onto-the-pasteboard concern https://github.com/dway123/raw-clipboard-access/issues/3 is very serious, and engineers from multiple browser engines have stated that (1) the current approach is a non-starter due to this problem, and (2) that a pickling approach would be far more palatable. See https://github.com/dway123/raw-clipboard-access/issues/3, https://github.com/mozilla/standards-positions/issues/206, and [the most recent TPAC minutes](https://lists.w3.org/Archives/Public/public-editing-tf/2019Oct/0004.html) for examples.

In your explainer, you say (emphasis mine):

> Pickling was not chosen as it does not meet the requirements desired for raw clipboard access. Namely, interoperability between native and web applications *could not be assured within a reasonable time-frame* through pickling.

Rephrasing, your concern with pickling is with *adoption*. Perhaps a more pressing adoption concern is that, without pickling, your API is unlikely to be adopted by other browser engines?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/406#issuecomment-542310250