LGTM2 Thanks for working with other vendors and significantly reducing the interop risk here! :)
On Wed, Jun 1, 2022 at 6:19 PM Alex Russell <[email protected]> wrote: > It's great to see all of this progress and the updated explainer is very > clear. > > LGTM1 > > On Wednesday, May 25, 2022 at 9:37:19 AM UTC-7 snianu wrote: > >> Reviving this thread and restarting the I2S process for this API…. >> >> Sorry for the delay here. We’ve been discussing the new proposal >> <https://github.com/w3c/clipboard-apis/issues/165> with EditingWG >> members and with our partners. We agree with Firefox’s proposal to use “web >> “ prefix for web custom formats instead of the unsanitized option. It makes >> the API more ergonomic and helps in interop across apps which is one of the >> benefits of using web custom formats. >> >> We have support from other browser vendors as well( >> https://github.com/w3c/clipboard-apis/issues/165#issuecomment-1047065265, >> https://github.com/w3c/clipboard-apis/issues/165#issue-1117218251). >> >> I’ll try to summarize the changes here. >> >> - We removed the `unsanitized` option from ClipboardItem constructor >> and read() method call. >> - We’re adding support to read/write MIME types that have “web >> “(“web” followed by U+0020 SPACE) prefix. These special formats would be >> read/written unsanitized from/to the system clipboard. It will follow the >> platform specific clipboard format naming convention that we previously >> proposed for pickling: >> >> https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#os-interaction-format-naming >> . >> - Web authors have access to both web custom format(which is >> unsanitized) and well-known formats(which is sanitized for text/html) >> during read(). In the previous proposal, unsanitized option controlled >> access to pickled formats, so if web authors provided well-known MIME >> types >> in the unsanitized list, then they only get access to custom unsanitized >> formats for the well-known mime types, and not the sanitized(for >> text/html) >> version for these mime types. >> - We’re adding transient user activation as a requirement for >> reading/writing all supported formats in the async clipboard API. The >> transient user activation requirement is something that affects the >> existing formats. We’ve added histograms to check if site is calling the >> async API without transient user activation. We don’t anticipate any >> issues >> with this extra check because we don’t expect the site to read clipboard >> data without any user interaction as that would be a severe >> security/privacy issue. We discussed this in the EditingWG meeting and >> everyone agrees that this check should be a strict requirement to access >> system clipboard. Here is the relevant issue and EditingWG meeting notes: >> https://github.com/w3c/clipboard-apis/issues/75#issuecomment-1088932790 >> & >> https://github.com/w3c/clipboard-apis/issues/75#issuecomment-1125148793 >> . >> - We’ve updated the spec, explainer and the current implementation. >> Spec: https://github.com/w3c/clipboard-apis/pull/175, Explainer: >> >> https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#web-custom-formats-for-async-clipboard-api, >> CL: https://chromium-review.googlesource.com/c/chromium/src/+/3650952 >> >> >> >> Please let us know if you have any questions/concerns. >> >> >> >> Thanks, >> >> Anupam >> >> >> >> *From:* Anupam Snigdha >> *Sent:* Thursday, February 3, 2022 9:06 AM >> *To:* 'Yoav Weiss' <[email protected]>; blink-dev < >> [email protected]> >> *Cc:* Philip Jägenstedt <[email protected]>; Domenic Denicola < >> [email protected]>; Chris Harrelson <[email protected]>; Daniel >> Bratell <[email protected]>; blink-dev <[email protected]>; Alex >> Russell <[email protected]>; Abhishek Rathi <[email protected]>; >> [email protected] <[email protected]>; Ajay Rahatekar < >> [email protected]>; Bo Cupp <[email protected]>; Marijn >> Kruisselbrink <[email protected]>; Joshua Bell <[email protected]>; >> Victor Costan <[email protected]>; Scott Low <[email protected]> >> *Subject:* RE: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling >> for Async Clipboard API >> >> >> >> Discussed offline. Sorry for the delay in response. We are reviewing >> Mozilla’s >> feedback on the proposal >> <https://github.com/w3c/clipboard-apis/issues/165> so I think we can put >> this intent on hold for now. >> >> >> >> Thanks, >> >> Anupam >> >> >> >> *From:* Yoav Weiss <[email protected]> >> *Sent:* Wednesday, February 2, 2022 2:26 AM >> *To:* blink-dev <[email protected]> >> *Cc:* Yoav Weiss <[email protected]>; Philip Jägenstedt < >> [email protected]>; Domenic Denicola <[email protected]>; Chris >> Harrelson <[email protected]>; Daniel Bratell <[email protected]>; >> blink-dev <[email protected]>; Alex Russell < >> [email protected]>; Abhishek Rathi <[email protected]>; >> [email protected] <[email protected]>; Ajay Rahatekar < >> [email protected]>; Bo Cupp <[email protected]>; Marijn >> Kruisselbrink <[email protected]>; Joshua Bell <[email protected]>; >> Victor Costan <[email protected]>; Scott Low <[email protected]>; >> Anupam Snigdha <[email protected]> >> *Subject:* Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling >> for Async Clipboard API >> >> >> >> Friendly ping! :) Also happy to discuss off-thread in case it's helpful. >> >> On Thursday, January 13, 2022 at 10:25:10 AM UTC+1 Yoav Weiss wrote: >> >> On Wed, Jan 12, 2022 at 8:33 PM Anupam Snigdha <[email protected]> >> wrote: >> >> Hi Philip, >> >> >> >> In the worst case we will be able to merge the pickling API changes >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fediting%2Fpull%2F383%2Ffiles&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944520917298%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=T3i273rZpIIB5sh8%2F9ec92LbeFj7Wjix9IShpSwW6gA%3D&reserved=0> >> into the EditingWG repo. We have a meeting this Friday with the Firefox >> folks to discuss the Pickling API as they were also interested in the >> proposal >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fclipboard-apis%2Fpull%2F162%23issuecomment-1007252874&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944520917298%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2BiVaeVKC1oxr2LN8Uzp5dKwHhEOB5NIG0UFPW5Mbxao%3D&reserved=0>. >> If we have consensus there, then we will be able to add pickling API to the >> official clipboard spec. >> >> Overall I think the algorithms required to implement Pickling API >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fediting%2Fpull%2F383%2Ffiles%23diff-f0d13f8afc0e1a5b023e28d5c8df456bc061ddd144b2354de8ab64c93d5ca8a2R1042&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944520917298%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=JzfKvne5BTU5u73g9Lu2ADxN3e3Ug0l%2BvYoEpyV%2BvSk%3D&reserved=0> >> is included in the forked PR. There are few concerns regarding >> sanitization, but we couldn’t come to an agreement with Apple folks >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fclipboard-apis%2Fissues%2F150%23issuecomment-917273986&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944520917298%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=o5LQhCcdCkeAgg8p8T6VUUcbkmfjfnEAiSLTIZTCpYk%3D&reserved=0> >> to standardize it. >> >> >> >> Regardless of venue and consensus, it seems important that you'd have a >> spec that clearly outlines what you are trying to ship here, so that if and >> when other vendors would like to follow (e.g. you mentioned Firefox are >> interested in following) they would be able to. >> >> >> >> Moreover all browsers have different sanitization behavior in the >> clipboard copy/paste methods so it will be hard to change anything there >> without breaking the legacy DataTransfer APIs that use the same >> sanitization algorithms. >> >> >> >> Thanks, >> >> Anupam >> >> >> >> *From:* Philip Jägenstedt <[email protected]> >> *Sent:* Wednesday, January 12, 2022 8:42 AM >> *To:* Anupam Snigdha <[email protected]> >> *Cc:* Domenic Denicola <[email protected]>; Chris Harrelson < >> [email protected]>; Daniel Bratell <[email protected]>; Yoav Weiss >> <[email protected]>; blink-dev <[email protected]>; Alex >> Russell <[email protected]>; Abhishek Rathi <[email protected]>; >> [email protected] <[email protected]>; [email protected] < >> [email protected]>; Bo Cupp <[email protected]>; [email protected] >> <[email protected]>; Joshua Bell <[email protected]>; Victor Costan < >> [email protected]>; Scott Low <[email protected]> >> *Subject:* Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling >> for Async Clipboard API >> >> >> >> Hi Anupam, >> >> >> >> Could https://w3c.github.io/gamepad/extensions.html >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fgamepad%2Fextensions.html&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944520917298%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=LgxL50MNEkah8lkxK9veCCxn4xGSkfXS2LbO1t%2BI1TM%3D&reserved=0> >> be a model to follow here? I think it's important to write down (and test) >> what you intend to ship in something that looks like a spec. If doing that >> in the EditingWG doesn't seem tractable, then the WICG is also an option. >> >> >> >> This seems like a fairly frustrating situation, but I hope it's clear >> what to try next. If you do feel like you're stuck with what to do with the >> spec, feel free to ask for advice here or off list. >> >> >> >> Best regards, >> >> Philip >> >> >> >> On Thu, Jan 6, 2022 at 8:16 PM Anupam Snigdha <[email protected]> >> wrote: >> >> Re: “but I guess it did not actually include the pickling parts yet!”: It >> does include the pickling parts. See the unsanitized option in the >> ClipboardItemOptions dictionary, write unsanitized format, os specific >> custom map name and os specific custom name sections in the PR for more >> details. >> >> >> >> The part that is missing is the one that you mentioned “what to do for >> non-text data types being written to the clipboard. (Ctrl+F for "This is >> left to the implementation..." in >> https://github.com/w3c/editing/pull/383/files >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fediting%2Fpull%2F383%2Ffiles&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944520967292%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=cK71DfuvNmPPBMy%2F6oJR%2BpJt9VT%2FBdE99xs3Y79%2B8QQ%3D&reserved=0> >> .) ” >> >> >> >> “I think it's still important to write a spec somewhere, even if the >> EditingWG does not host it” – We will be merging this into the Editing >> repo, but it wouldn’t be part of the official clipboard API spec due to >> disagreement with Apple. Looks like FF is also interested >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fclipboard-apis%2Fissues%2F150%23issuecomment-918063550&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944520967292%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=hJrJ9JSIHnQXGVZIS8KQWySxYQLhncOo12h0AqEGswk%3D&reserved=0> >> in standardizing the sanitization behavior because the legacy DataTransfer >> APIs behave the same in Chromium, FF, old Edge and IE, but since Apple >> opposed to these changes we couldn’t include it in the official clipboard >> API spec. >> >> >> >> *From:* Domenic Denicola <[email protected]> >> *Sent:* Thursday, January 6, 2022 11:01 AM >> *To:* Anupam Snigdha <[email protected]> >> *Cc:* Domenic Denicola <[email protected]>; Chris Harrelson < >> [email protected]>; Philip Jägenstedt <[email protected]>; Daniel >> Bratell <[email protected]>; Yoav Weiss <[email protected]>; >> blink-dev <[email protected]>; Alex Russell < >> [email protected]>; Abhishek Rathi <[email protected]>; >> [email protected] <[email protected]>; [email protected] < >> [email protected]>; Bo Cupp <[email protected]>; [email protected] >> <[email protected]>; Joshua Bell <[email protected]>; Victor Costan < >> [email protected]>; Scott Low <[email protected]> >> *Subject:* Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling >> for Async Clipboard API >> >> >> >> >> >> >> >> On Thu, Jan 6, 2022 at 1:24 PM Anupam Snigdha <[email protected]> >> wrote: >> >> Hi Domenic, >> >> >> >> I haven’t changed that part of the algorithm as I’m still working on the >> async >> API PR >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fclipboard-apis%2Fpull%2F158&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944520967292%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=7UWgKvgfGq8IVYjsV%2FiNRZZdo4gMZtuEaQbqxXIFa%2Bc%3D&reserved=0>. >> Once that PR is completed, I’ll fill in all the missing steps in the async >> clipboard API algorithms that are applicable for pickling. >> >> >> >> Thanks for the clarification. It was confusing since your message said >> "here is the PR for the pickling API" but I guess it did not actually >> include the pickling parts yet! >> >> >> >> I have added all the algorithms needed to read/write custom formats and >> the unsanitized option that we introduced in the ClipboardItemOptions >> dictionary. Note that the sanitized copy part is still left up to the >> implementors as we couldn’t come to an agreement in EditingWG >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fclipboard-apis%2Fissues%2F150%23issuecomment-994181053&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944520967292%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=JG4JK55d98sUyGl85KzfI1pyRONnrQyUF9ZQHDN5vV4%3D&reserved=0> >> . >> >> >> >> I think it's still important to write a spec somewhere, even if the >> EditingWG does not host it. See >> https://www.chromium.org/blink/guidelines/web-platform-changes-guidelines >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.chromium.org%2Fblink%2Fguidelines%2Fweb-platform-changes-guidelines&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944520967292%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=NOo1fSslGtD0fhKiqnn9Cdm3ma00GZOWeCmGgWAw8f8%3D&reserved=0> >> for more on why specifications are important even if they're not standards. >> >> >> >> >> >> -Anupam >> >> >> >> *From:* Domenic Denicola <[email protected]> >> *Sent:* Thursday, January 6, 2022 9:52 AM >> *To:* Anupam Snigdha <[email protected]> >> *Cc:* Chris Harrelson <[email protected]>; Philip Jägenstedt < >> [email protected]>; Daniel Bratell <[email protected]>; Yoav Weiss < >> [email protected]>; blink-dev <[email protected]>; Alex >> Russell <[email protected]>; Abhishek Rathi <[email protected]>; >> [email protected] <[email protected]>; [email protected] < >> [email protected]>; Bo Cupp <[email protected]>; [email protected] >> <[email protected]>; Joshua Bell <[email protected]>; Victor Costan < >> [email protected]>; Scott Low <[email protected]> >> *Subject:* Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling >> for Async Clipboard API >> >> >> >> >> >> >> >> On Wed, Jan 5, 2022 at 9:01 PM 'Anupam Snigdha' via blink-dev < >> [email protected]> wrote: >> >> Here is the PR for pickling API: https://github.com/w3c/editing/pull/383 >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fediting%2Fpull%2F383&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944520967292%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=U1csLB02nTWEhEdjRlm%2BhiUZougwAsDFn77zZ2GkbC4%3D&reserved=0> >> >> >> >> Note that unfortunately the most important part of the spec is left to >> the implementation: i.e., what to do for non-text data types being written >> to the clipboard. (Ctrl+F for "This is left to the implementation..." in >> https://github.com/w3c/editing/pull/383/files >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fediting%2Fpull%2F383%2Ffiles&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944520967292%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=cK71DfuvNmPPBMy%2F6oJR%2BpJt9VT%2FBdE99xs3Y79%2B8QQ%3D&reserved=0> >> .) If I understand correctly, that is what pickling is all about, so I'm >> not sure pickling actually has an interoperably-implementable >> specification... >> >> >> >> >> >> *From:* Anupam Snigdha >> *Sent:* Wednesday, January 5, 2022 9:41 AM >> *To:* 'Chris Harrelson' <[email protected]> >> *Cc:* Philip Jägenstedt <[email protected]>; Daniel Bratell < >> [email protected]>; Yoav Weiss <[email protected]>; blink-dev < >> [email protected]>; Alex Russell <[email protected]>; >> Abhishek Rathi <[email protected]>; [email protected] <[email protected]>; >> [email protected] <[email protected]>; Bo Cupp < >> [email protected]>; [email protected] <[email protected]>; Joshua Bell < >> [email protected]>; Victor Costan <[email protected]>; Scott Low < >> [email protected]> >> *Subject:* RE: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling >> for Async Clipboard API >> >> >> >> Hi Chris, >> >> >> >> Happy new year to you too 😊. Yes, the text would be in spec language, >> but it won’t be part of the clipboard API spec >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fclipboard-apis%2F&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944520967292%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=bFmLvBk23dUecqrDVHAa4xZRDJHMFHfkV72%2FxmMFwAE%3D&reserved=0> >> (at least for now). I’m almost done with the changes. Will upload it to >> EditingWG by today EOD. >> >> I’ve also addressed all comments on the async API PR >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fclipboard-apis%2Fpull%2F158&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521017283%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=b1FaoSgDPLowlevguDzF5oe0OgDeK3fyYS7UWfJkrmY%3D&reserved=0>, >> but it is unrelated to pickling. This PR addresses all concerns about the >> async clipboard API spec in general. >> >> >> >> Thanks, >> >> Anupam >> >> >> >> *From:* Chris Harrelson <[email protected]> >> *Sent:* Wednesday, January 5, 2022 8:35 AM >> *To:* Anupam Snigdha <[email protected]> >> *Cc:* Philip Jägenstedt <[email protected]>; Daniel Bratell < >> [email protected]>; Yoav Weiss <[email protected]>; blink-dev < >> [email protected]>; Alex Russell <[email protected]>; >> Abhishek Rathi <[email protected]>; [email protected] <[email protected]>; >> [email protected] <[email protected]>; Bo Cupp < >> [email protected]>; [email protected] <[email protected]>; Joshua Bell < >> [email protected]>; Victor Costan <[email protected]>; Scott Low < >> [email protected]> >> *Subject:* Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling >> for Async Clipboard API >> >> >> >> Hi Anupam, >> >> >> >> Happy new year. >> >> >> >> When you say "article" in WICG or EditingWG do you mean spec? If so, that >> sounds fine. >> >> >> >> On Fri, Dec 17, 2021 at 1:21 PM 'Anupam Snigdha' via blink-dev < >> [email protected]> wrote: >> >> Hi Philip, >> >> >> >> Yes, https://github.com/w3c/clipboard-apis/pull/162 >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fclipboard-apis%2Fpull%2F162&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521017283%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=T4rlz0Pb6HP2rM56CxKe5brovz9P6Q2OI5KZIhA0oj4%3D&reserved=0> >> is >> blocked on adding the `unsanitized` option to the clipboard API spec. Since >> we cannot come to an agreement, we decided to write up an article about it >> and publish it either in EditingWG or WICG. We want to write something in >> the clipboard API spec about the native custom format map and how that >> would be parsed by native apps in specific platforms , so I'll remove the >> `unsanitized` option from the spec PR and just add this info as non >> normative notes because Apple is still opposed to standardize any native >> clipboard formats in a web spec -- They want this to be defined by the OS. >> >> >> >> Thanks, >> >> Anupam >> ------------------------------ >> >> *From:* Philip Jägenstedt <[email protected]> >> *Sent:* Thursday, December 16, 2021 7:12 AM >> *To:* Anupam Snigdha <[email protected]> >> *Cc:* Daniel Bratell <[email protected]>; Yoav Weiss < >> [email protected]>; blink-dev <[email protected]>; Alex >> Russell <[email protected]>; Abhishek Rathi <[email protected]>; >> [email protected] <[email protected]>; [email protected] < >> [email protected]>; Bo Cupp <[email protected]>; [email protected] >> <[email protected]>; Joshua Bell <[email protected]>; Victor Costan < >> [email protected]>; Scott Low <[email protected]> >> *Subject:* Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling >> for Async Clipboard API >> >> >> >> Hi Anupam, >> >> >> >> It sounds like https://github.com/w3c/clipboard-apis/pull/162 >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fclipboard-apis%2Fpull%2F162&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521017283%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=T4rlz0Pb6HP2rM56CxKe5brovz9P6Q2OI5KZIhA0oj4%3D&reserved=0> >> is blocked on the objections, and thus the `unsanitized` option won't be in >> https://w3c.github.io/clipboard-apis/ >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fclipboard-apis%2F&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521017283%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=HhFmJ9ODNd%2BesZ6y2GhpXrdEhaKSCDg3KmBfW5kPtKU%3D&reserved=0>. >> If we ship this, will it be defined by any spec? Is it an option to take >> this proposal to the WICG? Although we ship things while spec PRs are open >> sometimes, when there's no expectation that the PR can be merged, I think >> we need to find an alternative place for it. >> >> >> >> Best regards, >> >> Philip >> >> >> >> On Wed, Dec 15, 2021 at 7:02 PM 'Anupam Snigdha' via blink-dev < >> [email protected]> wrote: >> >> Re origin trial: We did discuss about origin trials, but we are not >> anticipating any changes to the web API. Note that `unsanitized` option is >> a member of `ClipboardItemOptions` dictionary and we are not changing the >> shape of the existing read/write methods. >> >> Also, since this feature would benefit a lot from changes in the native >> apps, we want to commit to the native format naming/structure for pickled >> format map. Native apps like Office have a different release cycle >> (depending on whether it is enterprise or not, it would vary a lot), and >> it’ll be really hard for them to make any changes if we decide to change >> either the naming or the JSON like structure of the format map. >> >> >> >> *From:* Daniel Bratell <[email protected]> >> *Sent:* Wednesday, December 15, 2021 8:40 AM >> *To:* Yoav Weiss <[email protected]>; blink-dev < >> [email protected]> >> *Cc:* Alex Russell <[email protected]>; Abhishek Rathi < >> [email protected]>; [email protected] <[email protected]>; Anupam Snigdha >> <[email protected]>; [email protected] <[email protected]>; >> Bo Cupp <[email protected]>; [email protected] <[email protected]>; Joshua >> Bell <[email protected]>; Victor Costan <[email protected]>; Scott >> Low <[email protected]> >> *Subject:* [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling for >> Async Clipboard API >> >> >> >> One idea I have here is that unless everyone agrees to a plan, this might >> be suitable for an origin trial. That would allow the major sites that have >> said they want this to try it out without locking ourselves into a certain >> API shape. >> >> /Daniel >> >> On 2021-12-15 17:21, Yoav Weiss wrote: >> >> Reading through the issues, I saw this comment >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fclipboard-apis%2Fissues%2F150%23issuecomment-994181053&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521017283%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=bGlkCndnXaVThJAihw2XbyD%2FYqTj2kJ7qXn453wSZOM%3D&reserved=0>, >> which suggests that the `unsantizied` option would be removed. That change >> is not yet reflected in the explainer >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fediting%2Fblob%2Fgh-pages%2Fdocs%2Fclipboard-pickling%2Fexplainer.md&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521017283%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=klsIXaPdxhVP8dugPqAyLv4WrAVWOAsSWNtUCWjo6Vw%3D&reserved=0>, >> and seems like a big change. >> >> >> >> Can you outline the plan? >> >> On Tuesday, December 14, 2021 at 1:02:55 AM UTC+1 Alex Russell wrote: >> >> Thanks for the feedback, Sean and Abishek. >> >> >> >> Sounds like strong developer support; hoping this will get resolved this >> week. >> >> On Thursday, December 9, 2021 at 10:04:09 AM UTC-8 Abhishek Rathi wrote: >> >> At Excel Online, we tried this in our dev environments have seen >> significant improvement in Copy Paste fidelity from desktop apps. This will >> improve user experience especially for app specific features like formulas, >> tables, etc. >> >> On Tuesday, 7 December, 2021 at 10:31:44 pm UTC+5:30 [email protected] >> wrote: >> >> Happy to see movement on this. Just a note to say that we would like to >> use this feature at Adobe, and would be interested in using it in Photoshop >> Web, Creative Cloud Canvas, and potentially other future web initiatives, >> particularly for interop with our desktop applications. (With the >> understanding, of course, that said applications would have to be updated >> to read the custom web format map.) >> >> >> >> Sean >> >> On Thursday, November 18, 2021 at 1:30:32 PM UTC-8 snianu 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 >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fediting%2Fblob%2Fgh-pages%2Fdocs%2Fclipboard-pickling%2Fexplainer.md%23pickling-for-async-clipboard-api&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521017283%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=zEh9ljgNFfLriIhFFMv96xw%2Bmec6X%2BnaKCzNLJ%2FVcjw%3D&reserved=0> >> Specification >> >> https://github.com/w3c/clipboard-apis/pull/162 >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fclipboard-apis%2Fpull%2F162&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521017283%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=T4rlz0Pb6HP2rM56CxKe5brovz9P6Q2OI5KZIhA0oj4%3D&reserved=0> >> >> 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%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521067279%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=WGUdAHr4o9wWEnK8ZXYtNZL0duDcTXmy2vWvIJRaWhg%3D&reserved=0> >> Design docs >> >> >> >> https://docs.google.com/document/d/1afc45MQuwxEWgoUeJCO-sOWRSzs31V4JS-kKXJNMTXw/edit >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1afc45MQuwxEWgoUeJCO-sOWRSzs31V4JS-kKXJNMTXw%2Fedit&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521067279%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=kO%2B4vA76maig7OUaUOEfNcEb9A56M%2BgVyTv4TBVP8yE%3D&reserved=0> >> 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Flist%3Fq%3Dcomponent%3ABlink%253EDataTransfer&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521067279%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=lh4WdfOLSufufBy%2Bg5Fmh8h%2FsuWofqtUS9r%2Ff9wq2E4%3D&reserved=0> >> Search tags >> >> pickle >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.chromestatus.com%2Ffeatures%23tags%3Apickle&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521067279%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=7B1S%2BbwFexgdTO7Qg7kDzD%2B619gEbKhKTNpV9LImi%2Fk%3D&reserved=0> >> , pickling api >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.chromestatus.com%2Ffeatures%23tags%3Apickling%2520api&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521067279%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=os%2BOWYO2YcdU2zVQM3rQa6PHCnUuFjqXMS9POY2aMwI%3D&reserved=0> >> , pickling >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.chromestatus.com%2Ffeatures%23tags%3Apickling&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521067279%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=E10RUgTh3%2B5ZcSZQKlKYiuR%2BPrZhJ6nSq4131tNmzg4%3D&reserved=0> >> , clipboard custom format >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.chromestatus.com%2Ffeatures%23tags%3Aclipboard%2520custom%2520format&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521067279%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=VZWPD6uQHVYeL3HvUl%2BC8nmE0bPFWwsOlmykajb2aRs%3D&reserved=0> >> TAG review >> >> https://github.com/w3ctag/design-reviews/issues/636 >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3ctag%2Fdesign-reviews%2Fissues%2F636&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521067279%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=4RuuHKtBeIJS%2F9lHDpPzCePI5YytmJXW0kgqImKvobA%3D&reserved=0> >> 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 >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmozilla%2Fstandards-positions%2Fissues%2F525&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521117281%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=VoxWhLHmARjfX6jHad%2FJ0CGxVGC0Aos0WBCiVEcPwWU%3D&reserved=0> >> ) >> >> *WebKit*: Neutral ( >> https://github.com/w3c/editing/issues/334#issuecomment-933939592 >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fediting%2Fissues%2F334%23issuecomment-933939592&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521117281%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=wjd6f%2B9mqePNpeethBlZr7vfh5BB%2BiZPQOstu2nmdqs%3D&reserved=0>) >> Webkit has a custom format implementation which isn't well documented. >> >> *Web developers*: Positive ( >> https://github.com/w3ctag/design-reviews/issues/636#issuecomment-854038820 >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3ctag%2Fdesign-reviews%2Fissues%2F636%23issuecomment-854038820&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521117281%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=p4aOIz%2BfaUFHyFzNajR%2BUMiZ3hh3ed4kkYs%2BoerSmD8%3D&reserved=0>) >> 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 >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fediting%2Fissues%2F315&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521117281%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=VfZmQHCvNgcUVvFYkWPNTUH6vyfW0JPCBbDmgo1iNuI%3D&reserved=0> >> >> >> 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromium.googlesource.com%2Fchromium%2Fsrc%2F%2B%2Fmaster%2Fdocs%2Ftesting%2Fweb_platform_tests.md&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521117281%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=86437BWrRDYSXt0N62gWs2f%2FfODtSVQlMQHbz4zWcuU%3D&reserved=0> >> ? >> >> Yes >> >> >> https://wpt.fyi/results/clipboard-apis?label=master&label=experimental&aligned&q=async%20clipboard >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwpt.fyi%2Fresults%2Fclipboard-apis%3Flabel%3Dmaster%26label%3Dexperimental%26aligned%26q%3Dasync%2520clipboard&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521117281%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Y8GWUWIGew1NuRaGPJpSkF0X5XXOvcl3Ec5NvrMqV9k%3D&reserved=0> >> >> >> https://wpt.fyi/results/clipboard-apis/async-custom-formats-write-read.tentative.https.html?label=master&label=experimental&aligned&q=async%20clipboard >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwpt.fyi%2Fresults%2Fclipboard-apis%2Fasync-custom-formats-write-read.tentative.https.html%3Flabel%3Dmaster%26label%3Dexperimental%26aligned%26q%3Dasync%2520clipboard&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521117281%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=7%2FeiB9knIvZ%2FHFJW1%2FIfPlqEukynDy79minEAj62UTM%3D&reserved=0> >> Flag name >> >> ClipboardCustomFormats >> Requires code in //chrome? >> >> False >> Tracking bug >> >> https://bugs.chromium.org/p/chromium/issues/detail?id=106449 >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D106449&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521117281%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=1z7t1PnpBhIxPZ2bZoTVUyplwLtTUHnFXQ5y6k52a%2BQ%3D&reserved=0> >> Sample links >> >> https://glitch.com/edit/#!/sequoia-innovative-date >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fglitch.com%2Fedit%2F%23!%2Fsequoia-innovative-date&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521167277%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=9g3Eb84jix0eBbC0qsQZdo9Vu4Fi%2Ft9Q27NqnY24Was%3D&reserved=0> >> Estimated milestones >> >> 98 >> >> >> Link to entry on the Chrome Platform Status >> >> https://www.chromestatus.com/feature/5649558757441536 >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.chromestatus.com%2Ffeature%2F5649558757441536&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521167277%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=4AJ49eVRYUDCRbJcpc5IJnPr0ZhUq%2BpclnJAWyU%2Bgso%3D&reserved=0> >> 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 >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fa%2Fchromium.org%2Fg%2Fblink-dev%2Fc%2FLo7WBM_v_LY%2Fm%2FLncCKkXeAwAJ%3Futm_medium%3Demail%26utm_source%3Dfooter&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521167277%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=dJFwObIShLXOZ9JvKHhPMJZc5A0Yj9yzD688iE23QTE%3D&reserved=0> >> >> This intent message was generated by Chrome Platform Status >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.chromestatus.com%2F&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521167277%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=zFrwh83zRiSg%2BW5L2wTcVfpeSYyM%2BbLtM1aMbMjQta8%3D&reserved=0> >> . >> >> >> >> -- >> 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/339fdf22-0449-4c3f-8d8e-f938a8f103e1n%40chromium.org >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fa%2Fchromium.org%2Fd%2Fmsgid%2Fblink-dev%2F339fdf22-0449-4c3f-8d8e-f938a8f103e1n%2540chromium.org%3Futm_medium%3Demail%26utm_source%3Dfooter&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521167277%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=t51yhKbQunAqp5AqSVvxpq6rf2O4CM3DJ410A8w2fEY%3D&reserved=0> >> . >> >> -- >> 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/SN6PR00MB0397C21E7158CFA831D5293FCF769%40SN6PR00MB0397.namprd00.prod.outlook.com >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fa%2Fchromium.org%2Fd%2Fmsgid%2Fblink-dev%2FSN6PR00MB0397C21E7158CFA831D5293FCF769%2540SN6PR00MB0397.namprd00.prod.outlook.com%3Futm_medium%3Demail%26utm_source%3Dfooter&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521167277%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Vr%2FmhRk7OugQVFREvceiujxDkMEcGJZZeQS9BJ%2Fw3Pw%3D&reserved=0> >> . >> >> -- >> 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/DM5PR00MB0391DCA80B2EE3D11F05936ACF789%40DM5PR00MB0391.namprd00.prod.outlook.com >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fa%2Fchromium.org%2Fd%2Fmsgid%2Fblink-dev%2FDM5PR00MB0391DCA80B2EE3D11F05936ACF789%2540DM5PR00MB0391.namprd00.prod.outlook.com%3Futm_medium%3Demail%26utm_source%3Dfooter&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521167277%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=7f4m2LBlCysJK6Y8YCtwovmjB6wHmBK7q4nNRI6VcYI%3D&reserved=0> >> . >> >> -- >> 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/SN6PR00MB0397684F4239584B6903C5BECF4C9%40SN6PR00MB0397.namprd00.prod.outlook.com >> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fa%2Fchromium.org%2Fd%2Fmsgid%2Fblink-dev%2FSN6PR00MB0397684F4239584B6903C5BECF4C9%2540SN6PR00MB0397.namprd00.prod.outlook.com%3Futm_medium%3Demail%26utm_source%3Dfooter&data=04%7C01%7Csnianu%40microsoft.com%7C1b2f9c4cb8c9437b1f5908d9e6365db5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637793944521167277%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=NrKJCVa56rPa55X0oRZAwZXoO1au3eNoQBQLAi0aY0I%3D&reserved=0> >> . >> >> -- 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/CAL5BFfX3TOEkmF%2BDpLX6zjHs1j%2Bp%2Bo6QHY6SCyv_vi-59a_g7w%40mail.gmail.com.
