Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) from Victor Costan on 2022-02-01 (public-webapps-github@w3.org from February 2022)

From: Victor Costan <notifications@github.com>
Date: Mon, 31 Jan 2022 17:03:15 -0800
To: w3c/clipboard-apis <clipboard-apis@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/clipboard-apis/pull/162/c1026373746@github.com>

I think this PR had some non-controversial parts that seem valuable. Would it make sense to try to get those merged separately?

For example, I think that the added lines 610-616, 623-648 (minus 636) document Async Clipboard API behavior that is either shipped or non-controversial (not related to sanitization, custom types, or permissions).

I'm hoping this would make it easier to compare proposals for the controversial pieces.

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

Message ID: <w3c/clipboard-apis/pull/162/c1026373746@github.com>

Received on Tuesday, 1 February 2022 01:03:27 UTC