Hi Anupam, I see that the two pull requests on the spec are still open: https://github.com/w3c/clipboard-apis/pull/158 https://github.com/w3c/clipboard-apis/pull/162
I see there's a lot of discussion on both, with folks from other vendors involved, and it looks like some points are contentious. Can you summarize the state of things as they are, and what you think the remaining steps are to landing the spec changes? On the testing front, is async-custom-formats-write-read.tentative.https.html <https://github.com/web-platform-tests/wpt/blob/dc91bc44ac/clipboard-apis/async-custom-formats-write-read.tentative.https.html> the only test for this? This test doesn't seem to cover what happens writing both text/plain and custom payload, and what then happens if pasting that with and without opting into the custom format. Can these tests be made more elaborate? Best regards, Philip On Thu, Nov 18, 2021 at 10:30 PM 'Anupam Snigdha' via blink-dev < [email protected]> wrote: > Contact emails > > [email protected], [email protected], [email protected] > > Explainer > > > https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#pickling-for-async-clipboard-api > > Specification > > https://github.com/w3c/clipboard-apis/pull/162 > > https://github.com/w3c/clipboard-apis/pull/158 > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fclipboard-apis%2Fpull%2F158&data=04%7C01%7Csnianu%40microsoft.com%7C8b8029008333441013f608d99fa25a2e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637716342126749866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2wJznVPiU1J8lxdyepM4cAMndT7vpm4MYSwI44EuzRQ%3D&reserved=0> > Design docs > > > > https://docs.google.com/document/d/1afc45MQuwxEWgoUeJCO-sOWRSzs31V4JS-kKXJNMTXw/edit > > Summary > > Pickle Clipboard API lets websites read and write arbitrary unsanitized > payloads using a standardized pickling format, as well as read and write a > limited subset of OS-specific formats (for supporting legacy apps). The > name of the clipboard format is mangled by the browser in a standardized > way to indicate that the content is from the web, which allows native > applications to opt-in to accepting the unsanitized content. > > > Blink component > > Blink>DataTransfer > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EDataTransfer> > > Search tags > > pickle <https://www.chromestatus.com/features#tags:pickle>, pickling api > <https://www.chromestatus.com/features#tags:pickling%20api>, pickling > <https://www.chromestatus.com/features#tags:pickling>, clipboard custom > format > <https://www.chromestatus.com/features#tags:clipboard%20custom%20format> > > TAG review > > https://github.com/w3ctag/design-reviews/issues/636 > > TAG review status > > Issues addressed > > Risks > > > Interoperability and Compatibility > > Other browsers implement an ability to write custom clipboard data in > varied shapes. Part of the value of this work is to standardize the names > of the formats that will be written per platform and to ensure a common > shape of data on the clipboard so that browsers can read and write from > this standard set of pickled formats. > > > *Gecko*: No signal ( > https://github.com/mozilla/standards-positions/issues/525) > > *WebKit*: Neutral ( > https://github.com/w3c/editing/issues/334#issuecomment-933939592) Webkit > has a custom format implementation which isn't well documented. > > *Web developers*: Positive ( > https://github.com/w3ctag/design-reviews/issues/636#issuecomment-854038820) > Positive signal from Figma & Sketchup. Internal MS office products have > shown interest in supporting this API. > > *Other signals*: > > Ergonomics > > This feature is part of the existing async clipboard read/write. It > doesn't affect the well-defined formats that are supported by this API. > > > Activation > > The feature uses the existing async clipboard read/write methods which has > already been shipped. > > > Security > > Here is a link to a more detailed security review: > https://github.com/w3c/editing/issues/315 > > > Debuggability > > The async clipboard APIs have basic tooling support as described in the > DevTools support checklist doc. > > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> > ? > > Yes > > > https://wpt.fyi/results/clipboard-apis?label=master&label=experimental&aligned&q=async%20clipboard > > > https://wpt.fyi/results/clipboard-apis/async-custom-formats-write-read.tentative.https.html?label=master&label=experimental&aligned&q=async%20clipboard > > Flag name > > ClipboardCustomFormats > > Requires code in //chrome? > > False > > Tracking bug > > https://bugs.chromium.org/p/chromium/issues/detail?id=106449 > > Sample links > > https://glitch.com/edit/#!/sequoia-innovative-date > > Estimated milestones > > 98 > > > Link to entry on the Chrome Platform Status > > https://www.chromestatus.com/feature/5649558757441536 > > Links to previous Intent discussions > > Intent to prototype: > https://groups.google.com/a/chromium.org/g/blink-dev/c/Lo7WBM_v_LY/m/LncCKkXeAwAJ?utm_medium=email&utm_source=footer > > This intent message was generated by Chrome Platform Status > <https://www.chromestatus.com/>. > > > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/SN6PR00MB0397FE5D4193AD46D210F220CF9B9%40SN6PR00MB0397.namprd00.prod.outlook.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/SN6PR00MB0397FE5D4193AD46D210F220CF9B9%40SN6PR00MB0397.namprd00.prod.outlook.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYfH93A7c6C9Y_KEL9wWuZPpo3GehJOH-9F9waS8qy2ipA%40mail.gmail.com.
