Hi Philip, Sorry for the delayed response. Sure, I can summarize the discussions both in the PR and the Github issues mentioned in the thread.
https://github.com/w3c/clipboard-apis/pull/158 This PR is essentially a rewrite of async clipboard API. Since the specification had lot of details missing on the ClipboardItem object and Navigator.Clipboard methods, we decided to work on this first before making any additional changes to the spec. Domenic and mbrodesser have been reviewing my changes(thank you for that!) and I think the spec is now in a pretty good state and should be ready to land soon. https://github.com/w3c/clipboard-apis/pull/162 This PR adds an `unsanitized` option to the ClipboardItemOptions dictionary which will be used to read/write unsanitized custom formats to the system clipboard. This is the custom formats support that we want to add to the async clipboard API. The contention is mainly on the usage of the `unsanitized` option. When web developers provide formats that they want the browsers to write to the clipboard without any sanitization, the `unsanitized` option helps us to determine which formats to pickle and add to the Web Custom Format Map<https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#os-interaction-format-naming>. If a site wants to read a custom format or an unsanitized version of the standard format<https://w3c.github.io/clipboard-apis/#mandatory-data-types-x>, then it needs to add those formats to the unsanitized list. If native apps want to read a custom format, then they have to query the Web Custom Format Map<https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#os-interaction-format-naming> first in order to get the custom format corresponding to the MIME type, and use that to query the system clipboard to fetch its content. The explainer has some examples<https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#pickling-write> as to how the web devs can read/write unsanitized custom formats, and how native apps can parse the Web Custom Format Map<https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#os-interaction-format-naming>. On Safari, the formats are always pickled so the need for unsanitized option is unnecessary on write. For read, Safari only provides access to the pickled formats if it is queried within the same origin. That limits the scope of the pickled formats read/write -- Native apps wouldn't be able to access the custom formats written by the web apps, and web apps wouldn't be able to access the custom formats if they are read from a different origin. We discussed extensively with the Editing WG members<https://github.com/w3c/editing/issues/334#issuecomment-933939592> and Apple devs were opposed to providing access to the custom formats via the unsanitized option. They want to provide a new OS clipboard platform API which native apps would have to use to explicitly query the custom formats. That apparently is a better option(in terms of security/privacy) than native apps explicitly adding code to access the custom formats from the clipboard without requiring to implement yet another platform API to read/write content from/to the clipboard, so we disagree with this approach. Moreover, this isn't something that we as browser developers have control over as adding an OS API is just not feasible for us, and we don't see the need to add a new platform API to read/write custom formats to the clipboard when the existing clipboard platform APIs provide read/write access to platform defined clipboard formats<https://docs.microsoft.com/en-us/windows/win32/dataxchg/standard-clipboard-formats> and custom formats<https://docs.microsoft.com/en-us/windows/win32/dataxchg/clipboard-formats#registered-clipboard-formats> defined by the native apps. We think that the unsanitized option is required for security as well as for performance reasons. It indicates explicitly which formats to pickle i.e. read/written without any sanitization process. The standard formats<https://w3c.github.io/clipboard-apis/#mandatory-data-types-x> are always sanitized by default, so reading without the unsanitized option will return a sanitized version of the standard format<https://w3c.github.io/clipboard-apis/#mandatory-data-types-x>. For custom formats web authors have to explicitly provide that in the unsanitized list that is passed in the read method call, which is a strong indication that they are aware of the security implications and know how to parse the content of the custom formats. We have been experimenting this API with the Excel native/web app devs and have received lot of positive feedback. Excel has implemented a custom workbook format that provides copying and pasting of rich content such as charts, Excel formulas, Word/Excel specific table/list semantics etc. This feature requires changes to the native app as well in order to read/write web custom formats, so we discussed the native format structure with the Editing WG members and didn't see any opposition. TAG members were also satisfied with the proposal<https://github.com/w3ctag/design-reviews/issues/636#issuecomment-919324784>. I'm working on adding more WPT tests in this CL: https://chromium-review.googlesource.com/c/chromium/src/+/3292370. Thanks, Anupam From: Philip Jägenstedt <foo...@chromium.org> Sent: Monday, November 22, 2021 2:44 AM To: Anupam Snigdha <sni...@microsoft.com> Cc: blink-dev <blink-dev@chromium.org>; ajayrahate...@google.com; Bo Cupp <pc...@microsoft.com>; m...@google.com; Joshua Bell <jsb...@chromium.org>; pwn...@chromium.org; Scott Low <sc...@microsoft.com> Subject: [EXTERNAL] Re: [blink-dev] Intent to Ship: Pickling for Async Clipboard API Hi Anupam, I see that the two pull requests on the spec are still open: 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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708416946%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=vzwcmw9wGE56K%2F7HzLB0maDA6oBYqcMAJjLaeAlTx0M%3D&reserved=0> 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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708416946%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=wn2jLd3glaFqk1jjeLOPQeqCM%2B9an8FcX1xoMHyZ%2B1w%3D&reserved=0> 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fweb-platform-tests%2Fwpt%2Fblob%2Fdc91bc44ac%2Fclipboard-apis%2Fasync-custom-formats-write-read.tentative.https.html&data=04%7C01%7Csnianu%40microsoft.com%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708466946%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=dFiWOEZ%2BZumwjqrS0%2FJM5jlVLOe0lRkF9XJgL%2FsKuTU%3D&reserved=0> 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 <blink-dev@chromium.org<mailto:blink-dev@chromium.org>> 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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708466946%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=li%2B57MPMjprGoOdMUw9HGMR49uhCYhXNZuPztOgRksU%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708466946%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=VJQW9vB22JqNZXA1GHlaLvc8L2iIMyQiX7z%2BTzbuaA0%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708466946%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=5ovbZ6CfRBHFbdolGYJWzHBQkLrRALuihJEgyaD6J8w%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708466946%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=iLfJba5EdsYjg4j6TESz31aUh8IaCVZfNhRDnOJKm70%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708466946%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=BKgYZsLl9vd6KURiWZPsXO%2FF4PQOxaRUPnCE3%2BcDUTw%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708516940%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=jpk0IXQLqAEjhHY%2FH3l6MJjpV5TSByRtngBA1TJetCk%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708516940%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=byvYsCxau5PK1mfbT7lDPuJhkw7E5mdr0EG1g52nJQI%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708516940%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=7QgX0eZ88vhWX4Jtn1xKHBQ5SkJ7%2Fnjr8Az4KmGAtdU%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708516940%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=jHycvWjONrXn5T0ewYPLFeIYiTGJBP6bSw%2BPfFGQ0ps%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708516940%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=DKpakJDpjWO5%2Bz64xWGGNa5zEphmLH2mWcYCARgG%2FYs%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708516940%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Btx%2FOqIh4qe4zsmF65aWLg5ZDomP83Q4gTJwT1sVwi4%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708566937%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=tWlfbrnkkb%2FXCeLWFzCFxMwyo4HWleupzDAT%2FZwl06U%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708566937%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=m9UrrYKGNPXRNx%2BiuxulD0xMJWMsVSElKc%2B%2FK2QChIk%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708566937%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Pu8%2Fh0MZGntQjswqkwx7hozc5lr%2Bntnsuvui68upZY0%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708566937%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=21ZkN5CJ%2B%2BMYdiIjN7bR6P06rJUmssBCEuaxVBghbhE%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708566937%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=fjgOV9wQ4mWv1Oh7DwiB%2FUGljMchvXnv%2BA9KQw7DTfs%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708566937%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ly68eNWPl9SZu%2BiH4KatVkGPL76nHwdnsQ9tB0krqSo%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708616941%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=IDBFf6D7veOQ%2FhdxQTzFSCPFqFs%2F9G4%2FEEq63Sy6yAI%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708616941%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=SHgVbiSIGN7dZK5YD9EzGOJp%2BOFloAvIjakRVLlWKfo%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708616941%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=NAVwvzktMV08KeSCYCXh1S8Qbj1RQUDwMpiw80rgAgU%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708616941%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=B3e3E5taHGQBLDvpefyFnJ%2FYbTnvefH8injRqEiCdpo%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%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708616941%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=r5ioAb1dFWWzvp4NhPoTJaO0SMA2rZdBRmkIQIRzFiY%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/SN6PR00MB0397FE5D4193AD46D210F220CF9B9%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%2FSN6PR00MB0397FE5D4193AD46D210F220CF9B9%2540SN6PR00MB0397.namprd00.prod.outlook.com%3Futm_medium%3Demail%26utm_source%3Dfooter&data=04%7C01%7Csnianu%40microsoft.com%7C687ebe19fa51443be3c408d9ada50d1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637731746708666936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Cp1RZ59ee9BZt2SQmWQpCqtiizStFiZZouzE7gLFG%2BY%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/SN6PR00MB03973F3687819B752073B67ACF669%40SN6PR00MB0397.namprd00.prod.outlook.com.
