Hi Philip, In the worst case we will be able to merge the pickling API changes<https://github.com/w3c/editing/pull/383/files> 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://github.com/w3c/clipboard-apis/pull/162#issuecomment-1007252874>. 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://github.com/w3c/editing/pull/383/files#diff-f0d13f8afc0e1a5b023e28d5c8df456bc061ddd144b2354de8ab64c93d5ca8a2R1042> is included in the forked PR. There are few concerns regarding sanitization, but we couldn’t come to an agreement with Apple folks<https://github.com/w3c/clipboard-apis/issues/150#issuecomment-917273986> to standardize it. 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 <foo...@chromium.org> Sent: Wednesday, January 12, 2022 8:42 AM To: Anupam Snigdha <sni...@microsoft.com> Cc: Domenic Denicola <dome...@chromium.org>; Chris Harrelson <chris...@chromium.org>; Daniel Bratell <bratel...@gmail.com>; Yoav Weiss <yoavwe...@chromium.org>; blink-dev <blink-dev@chromium.org>; Alex Russell <slightly...@chromium.org>; Abhishek Rathi <rath...@gmail.com>; svo...@gmail.com <svoi...@gmail.com>; ajayra...@google.com <ajayrahate...@google.com>; Bo Cupp <pc...@microsoft.com>; m...@google.com <m...@google.com>; Joshua Bell <jsb...@chromium.org>; Victor Costan <pwn...@chromium.org>; Scott Low <sc...@microsoft.com> 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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231225029%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=xevo3FUZt0QdPDem3IO4b%2F%2BnTLu8nNo8hMRosKwD8ec%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 <sni...@microsoft.com<mailto:sni...@microsoft.com>> 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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231225029%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2BPgztqUrzYjQS8%2BTWL0TaNiITF10gG9lfyAQh07elEs%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231225029%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=TGD8p98YFziRvjZS33kVXgBi8v0vTMjg%2BA5LD7fTrrQ%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 <dome...@chromium.org<mailto:dome...@chromium.org>> Sent: Thursday, January 6, 2022 11:01 AM To: Anupam Snigdha <sni...@microsoft.com<mailto:sni...@microsoft.com>> Cc: Domenic Denicola <dome...@chromium.org<mailto:dome...@chromium.org>>; Chris Harrelson <chris...@chromium.org<mailto:chris...@chromium.org>>; Philip Jägenstedt <foo...@chromium.org<mailto:foo...@chromium.org>>; Daniel Bratell <bratel...@gmail.com<mailto:bratel...@gmail.com>>; Yoav Weiss <yoavwe...@chromium.org<mailto:yoavwe...@chromium.org>>; blink-dev <blink-dev@chromium.org<mailto:blink-dev@chromium.org>>; Alex Russell <slightly...@chromium.org<mailto:slightly...@chromium.org>>; Abhishek Rathi <rath...@gmail.com<mailto:rath...@gmail.com>>; svo...@gmail.com<mailto:svo...@gmail.com> <svoi...@gmail.com<mailto:svoi...@gmail.com>>; ajayra...@google.com<mailto:ajayra...@google.com> <ajayrahate...@google.com<mailto:ajayrahate...@google.com>>; Bo Cupp <pc...@microsoft.com<mailto:pc...@microsoft.com>>; m...@google.com<mailto:m...@google.com> <m...@google.com<mailto:m...@google.com>>; Joshua Bell <jsb...@chromium.org<mailto:jsb...@chromium.org>>; Victor Costan <pwn...@chromium.org<mailto:pwn...@chromium.org>>; Scott Low <sc...@microsoft.com<mailto:sc...@microsoft.com>> 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 <sni...@microsoft.com<mailto:sni...@microsoft.com>> 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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231225029%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=qL2mzXy5CHhbwZ1J%2F3bJrRox%2BCXXmct4Vk06exYS12s%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231225029%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=zh4lPE2eB%2FrNfun8SlyuUuQyiC3DyejnOYAKqzXgcpA%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231275040%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=cAEWyzo%2BZGu68KhshGCljFaXNDfFS1NDfyEYG0LhpF8%3D&reserved=0> for more on why specifications are important even if they're not standards. -Anupam From: Domenic Denicola <dome...@chromium.org<mailto:dome...@chromium.org>> Sent: Thursday, January 6, 2022 9:52 AM To: Anupam Snigdha <sni...@microsoft.com<mailto:sni...@microsoft.com>> Cc: Chris Harrelson <chris...@chromium.org<mailto:chris...@chromium.org>>; Philip Jägenstedt <foo...@chromium.org<mailto:foo...@chromium.org>>; Daniel Bratell <bratel...@gmail.com<mailto:bratel...@gmail.com>>; Yoav Weiss <yoavwe...@chromium.org<mailto:yoavwe...@chromium.org>>; blink-dev <blink-dev@chromium.org<mailto:blink-dev@chromium.org>>; Alex Russell <slightly...@chromium.org<mailto:slightly...@chromium.org>>; Abhishek Rathi <rath...@gmail.com<mailto:rath...@gmail.com>>; svo...@gmail.com<mailto:svo...@gmail.com> <svoi...@gmail.com<mailto:svoi...@gmail.com>>; ajayra...@google.com<mailto:ajayra...@google.com> <ajayrahate...@google.com<mailto:ajayrahate...@google.com>>; Bo Cupp <pc...@microsoft.com<mailto:pc...@microsoft.com>>; m...@google.com<mailto:m...@google.com> <m...@google.com<mailto:m...@google.com>>; Joshua Bell <jsb...@chromium.org<mailto:jsb...@chromium.org>>; Victor Costan <pwn...@chromium.org<mailto:pwn...@chromium.org>>; Scott Low <sc...@microsoft.com<mailto:sc...@microsoft.com>> 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 <blink-dev@chromium.org<mailto:blink-dev@chromium.org>> 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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231275040%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=kU%2FtpAIGF0Ea7hDPXwwBNGOtytqiIsWMy%2FHdIztJBJw%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231275040%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=nDSp2fMUzit43lud2g2uQ55RLYhxfI5LSrAKeKtIGlk%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' <chris...@chromium.org<mailto:chris...@chromium.org>> Cc: Philip Jägenstedt <foo...@chromium.org<mailto:foo...@chromium.org>>; Daniel Bratell <bratel...@gmail.com<mailto:bratel...@gmail.com>>; Yoav Weiss <yoavwe...@chromium.org<mailto:yoavwe...@chromium.org>>; blink-dev <blink-dev@chromium.org<mailto:blink-dev@chromium.org>>; Alex Russell <slightly...@chromium.org<mailto:slightly...@chromium.org>>; Abhishek Rathi <rath...@gmail.com<mailto:rath...@gmail.com>>; svo...@gmail.com<mailto:svo...@gmail.com> <svoi...@gmail.com<mailto:svoi...@gmail.com>>; ajayra...@google.com<mailto:ajayra...@google.com> <ajayrahate...@google.com<mailto:ajayrahate...@google.com>>; Bo Cupp <pc...@microsoft.com<mailto:pc...@microsoft.com>>; m...@google.com<mailto:m...@google.com> <m...@google.com<mailto:m...@google.com>>; Joshua Bell <jsb...@chromium.org<mailto:jsb...@chromium.org>>; Victor Costan <pwn...@chromium.org<mailto:pwn...@chromium.org>>; Scott Low <sc...@microsoft.com<mailto:sc...@microsoft.com>> 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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231275040%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=6cg0tAOEMp41hb6Rq5FRoADdh939GIqm1f3vWNJYUKA%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231275040%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Aj%2F5B3kCgCzSUiBce5oLBRX5KrQuDJO1AwXczkNYbXo%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 <chris...@chromium.org<mailto:chris...@chromium.org>> Sent: Wednesday, January 5, 2022 8:35 AM To: Anupam Snigdha <sni...@microsoft.com<mailto:sni...@microsoft.com>> Cc: Philip Jägenstedt <foo...@chromium.org<mailto:foo...@chromium.org>>; Daniel Bratell <bratel...@gmail.com<mailto:bratel...@gmail.com>>; Yoav Weiss <yoavwe...@chromium.org<mailto:yoavwe...@chromium.org>>; blink-dev <blink-dev@chromium.org<mailto:blink-dev@chromium.org>>; Alex Russell <slightly...@chromium.org<mailto:slightly...@chromium.org>>; Abhishek Rathi <rath...@gmail.com<mailto:rath...@gmail.com>>; svo...@gmail.com<mailto:svo...@gmail.com> <svoi...@gmail.com<mailto:svoi...@gmail.com>>; ajayra...@google.com<mailto:ajayra...@google.com> <ajayrahate...@google.com<mailto:ajayrahate...@google.com>>; Bo Cupp <pc...@microsoft.com<mailto:pc...@microsoft.com>>; m...@google.com<mailto:m...@google.com> <m...@google.com<mailto:m...@google.com>>; Joshua Bell <jsb...@chromium.org<mailto:jsb...@chromium.org>>; Victor Costan <pwn...@chromium.org<mailto:pwn...@chromium.org>>; Scott Low <sc...@microsoft.com<mailto:sc...@microsoft.com>> 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 <blink-dev@chromium.org<mailto:blink-dev@chromium.org>> 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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231275040%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ah1SFU7%2FeCVHTUcoGgU8ldXL83Po7AWyi%2BZ7pVDx05U%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 <foo...@chromium.org<mailto:foo...@chromium.org>> Sent: Thursday, December 16, 2021 7:12 AM To: Anupam Snigdha <sni...@microsoft.com<mailto:sni...@microsoft.com>> Cc: Daniel Bratell <bratel...@gmail.com<mailto:bratel...@gmail.com>>; Yoav Weiss <yoavwe...@chromium.org<mailto:yoavwe...@chromium.org>>; blink-dev <blink-dev@chromium.org<mailto:blink-dev@chromium.org>>; Alex Russell <slightly...@chromium.org<mailto:slightly...@chromium.org>>; Abhishek Rathi <rath...@gmail.com<mailto:rath...@gmail.com>>; svo...@gmail.com<mailto:svo...@gmail.com> <svoi...@gmail.com<mailto:svoi...@gmail.com>>; ajayra...@google.com<mailto:ajayra...@google.com> <ajayrahate...@google.com<mailto:ajayrahate...@google.com>>; Bo Cupp <pc...@microsoft.com<mailto:pc...@microsoft.com>>; m...@google.com<mailto:m...@google.com> <m...@google.com<mailto:m...@google.com>>; Joshua Bell <jsb...@chromium.org<mailto:jsb...@chromium.org>>; Victor Costan <pwn...@chromium.org<mailto:pwn...@chromium.org>>; Scott Low <sc...@microsoft.com<mailto:sc...@microsoft.com>> 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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231275040%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ah1SFU7%2FeCVHTUcoGgU8ldXL83Po7AWyi%2BZ7pVDx05U%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231275040%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=6cg0tAOEMp41hb6Rq5FRoADdh939GIqm1f3vWNJYUKA%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 <blink-dev@chromium.org<mailto:blink-dev@chromium.org>> 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 <bratel...@gmail.com<mailto:bratel...@gmail.com>> Sent: Wednesday, December 15, 2021 8:40 AM To: Yoav Weiss <yoavwe...@chromium.org<mailto:yoavwe...@chromium.org>>; blink-dev <blink-dev@chromium.org<mailto:blink-dev@chromium.org>> Cc: Alex Russell <slightly...@chromium.org<mailto:slightly...@chromium.org>>; Abhishek Rathi <rath...@gmail.com<mailto:rath...@gmail.com>>; svo...@gmail.com<mailto:svo...@gmail.com> <svoi...@gmail.com<mailto:svoi...@gmail.com>>; Anupam Snigdha <sni...@microsoft.com<mailto:sni...@microsoft.com>>; ajayra...@google.com<mailto:ajayra...@google.com> <ajayrahate...@google.com<mailto:ajayrahate...@google.com>>; Bo Cupp <pc...@microsoft.com<mailto:pc...@microsoft.com>>; m...@google.com<mailto:m...@google.com> <m...@google.com<mailto:m...@google.com>>; Joshua Bell <jsb...@chromium.org<mailto:jsb...@chromium.org>>; Victor Costan <pwn...@chromium.org<mailto:pwn...@chromium.org>>; Scott Low <sc...@microsoft.com<mailto:sc...@microsoft.com>> 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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231275040%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=gDtlm6DJ4qc%2FS0uSKkDtKyJWxBuGSVwqpqcFSROIah4%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231275040%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=CJ4z6UHXOMmD0z0BSLPgH6Oi088hNc%2BFMe46oKJUo0s%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 svo...@gmail.com<mailto:svo...@gmail.com> 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 sni...@microsoft.com<mailto:sni...@microsoft.com>, m...@chromium.org<mailto:m...@chromium.org>, pc...@microsoft.com<mailto:pc...@microsoft.com> 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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231325033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=yI6YpHClqXEnLAo2jNEcWMg74QMRekt4PaDCyNLU%2FJ0%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231325033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=u4lyBYzNrKOBC7S0y4CI6%2BwkxT%2F2gsm8HDRY96RjjfU%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231325033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ZudLA6XTJtQbPi8wQB3Z6atKrltzzwtF5gTMmGcASqc%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231325033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=gGcqORbusSQA3NxrszTHDUd%2BTKPR35T3y1nnKfqxvpQ%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231325033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=OuHBVEITJR8VO3TH8aD2L%2Fy0bTyewqqmiVuL3qgSGwA%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231325033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=MnUHwEHurov4GITEOySdfR%2Fqci2o%2FAcD1S55VA%2FbH%2Bo%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231325033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=00APanSFBTLugDvPIc7%2BKJ1zmE2lbCcZ%2FPvrTa4CJfM%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231325033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=vvcUSozw7bCAk0ZrvhwLqL2rU4yUXYDYKesDLE%2BVQY8%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231325033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=N782bZICCMBTZh7CU3FOUogdxMt0CytnJ6WG9pbjTUY%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231325033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=6FCngGvoqW3X%2FsVSFTZdSFPj%2BYIEpSrEQGMno8Q%2BkAs%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231375021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ruWbBSkjGjcblf%2BaY1xuTMnHrlFuzrVtKhlsDhywOM0%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231375021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=TmOxVucYOcp5N30aLe7F6gWHYHjLV29rCD5WCGl5ojE%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231375021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2FgzuNwpWPGiAch2kttQptHKTM5NtKpS4NvCZZ32hZxM%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231375021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=xE0vwxiTwBZT99h1lBNjI3obgBEzy239p0Aoi1K9cfs%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231375021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=pV7YvyqBoBEsJ2fO1%2FnggpKM7K4Ky%2FGUrisgGlb579Q%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231375021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=uy%2BHBMBe3oTG5HrbiOHNdsoDvFl8RO8p5HimSyxt3E4%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231375021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=sEIwn6FeuKc8Klp%2BN0e8BNEE2qAI%2Fitriy051LKB2nM%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231375021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Tc0aQaqV%2FM6y7KrFdF9wnf12lZ2AQy1%2BekbkjFfZe9I%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231375021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2BRBzJCjWJOD8iTNOzpvPOFxWjw8fiWgnEe5iDHMOjnc%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231375021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Zux3N4nz2ZWFUUnwRw%2Ff8cFZriyqE0f6IQUubbtV0so%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231375021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=QpEUd%2BKcJ5CpXCugVuv4enJ53%2BnuRHyrSSDw0wryB0Y%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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231425016%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=GamaYLGFKbdu8%2FgmVhLx3k%2BvXvpTVkwoYrtlrliYDks%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 blink-dev+unsubscr...@chromium.org<mailto:blink-dev+unsubscr...@chromium.org>. 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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231425016%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Ofj%2FoYJNgaPMGw%2BtYi8vLYI%2FvLG1Wb1568%2FcTuSu%2Ft8%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 blink-dev+unsubscr...@chromium.org<mailto:blink-dev+unsubscr...@chromium.org>. 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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231425016%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=CLP6ZyZx6Pt6ovPloVgsym8kGV66D96zUVfY9P7A%2FeY%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 blink-dev+unsubscr...@chromium.org<mailto:blink-dev+unsubscr...@chromium.org>. 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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231425016%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=oWDedgo4WzF5Wd5hw3IdYf7Yw7QweA50lcsCBQNGByU%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 blink-dev+unsubscr...@chromium.org<mailto:blink-dev+unsubscr...@chromium.org>. 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%7Cb438a00fe81043d13f5108d9d5ea7182%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637776025231425016%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=qJeRVK9INPQeUCM5O3Wr%2FgoqDRA%2FpK%2B3Groai7wLtR0%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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/DM5PR00MB0391CDB1BECF825FC0C2C2E8CF529%40DM5PR00MB0391.namprd00.prod.outlook.com.
