Could I get clarification on the #clipboard-unsanitized-content flag?
When I enable this the Async API writes unsanitized html which is great but
when I call the following I don't see a new html and the original
"text/html" is still sanitized. I am testing against 107 beta on
10/21/2022. I have read the docs but I am unclear of the final
decision/implementation.
navigator.clipboard.read({
unsanitized: true
})
My goals is to have interop copy/paste with Excel desktop (2019)
Thanks
On Thursday, July 14, 2022 at 1:15:29 PM UTC-4 Ana Sollano Kim wrote:
> Thanks for the comments and clarifications on the feature.
>
>
>
> *From:* Anupam Snigdha <sni...@microsoft.com>
> *Sent:* Wednesday, July 13, 2022 10:47 AM
> *To:* Thomas Steiner <to...@google.com>
> *Cc:* Ana Sollano Kim <ana.s...@microsoft.com>; Bo Cupp <
> pc...@microsoft.com>; blin...@chromium.org
> *Subject:* RE: [EXTERNAL] Re: [blink-dev] Intent to prototype: Align
> async API read/write HTML format with DataTransfer API
>
>
>
> The unsanitized option being proposed here is only for the well-known HTML
> format. It could be extended to other well-known formats, but for now we
> are focusing on the HTML format. Web custom format is unsanitized by
> design, so this option doesn’t affect the existing web custom formats.
>
>
>
> *From:* Thomas Steiner <to...@google.com>
> *Sent:* Wednesday, July 13, 2022 9:56 AM
> *To:* Anupam Snigdha <sni...@microsoft.com>
> *Cc:* Ana Sollano Kim <ana.s...@microsoft.com>; Bo Cupp <
> pc...@microsoft.com>; Thomas Steiner <to...@google.com>;
> blin...@chromium.org
> *Subject:* Re: [EXTERNAL] Re: [blink-dev] Intent to prototype: Align
> async API read/write HTML format with DataTransfer API
>
>
>
> Just to clarify on my end, I was referring to the “Web Custom formats for
> Async Clipboard API” explainer (
> https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md
>
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fediting%2Fblob%2Fgh-pages%2Fdocs%2Fclipboard-pickling%2Fexplainer.md&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180455345%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fXhmmWiqMt6l6mOcV3DvemnuH1yObaUgwB10Z6nobvw%3D&reserved=0>).
>
> I was under the impression that this would replace the previous
> `unsanitized: true` flag (
>
>
> https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#alternative-considered-unsanitizedtrue
>
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fediting%2Fblob%2Fgh-pages%2Fdocs%2Fclipboard-pickling%2Fexplainer.md%23alternative-considered-unsanitizedtrue&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180455345%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KFbs1dUOSdqKeo2J7x0S%2BGYp1Xz%2BXJ16yr4ElF9uwro%3D&reserved=0>
> ).
>
>
>
> On Wed 13. Jul 2022 at 18:41 Anupam Snigdha <sni...@microsoft.com> wrote:
>
> Just to clarify some of the points in the explainer. This proposal
> introduces an `unsanitized` option only in the navigator.clipboard.read()
> method. For write() we will always write unsanitized HTML content to the
> clipboard. This will align the behavior of async APIs with the DataTransfer
> APIs and also be backward compatible with the native apps on certain
> platforms like Windows that rely on this behavior. With the current
> sanitization in async API, copy pasting HTML content in Office native apps
> is broken because we remove custom styles from the HTML markup, inline
> styles into the fragment that increases the size of the copy payload etc
> when we write the HTML format to the system clipboard.
>
>
>
> This proposal is a Chromium specific change because Firefox and Safari
> opposed to having an unsanitized option in the read() method, but they agreed
> to align the behavior of async APIs with DataTransfer APIs
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fclipboard-apis%2Fissues%2F150%23issuecomment-1033465241&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180455345%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=p7KJVjtDvlIIOLuHAJlxyx8AiCLoLR5SslyfQ7JKxVQ%3D&reserved=0>.
>
> We shipped the sanitization behavior first, so changing that would be a
> breaking change for us. Safari has the sanitization behavior for
> cross-origin copy-paste, but for same origin, they allow access to
> unsanitized HTML content. Safari’s async APIs behavior is aligned with the
> DataTransfer APIs so they don’t want to add an unsanitized option to read()
> method and cause backward compatibility issues. Firefox behaves the same as
> Chromium, but we didn’t see any support from them for adding an unsanitized
> option in read() method to allow web authors to access unsanitized HTML
> content.
>
> Even though the usage of async read
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromestatus.com%2Fmetrics%2Ffeature%2Fpopularity%23AsyncClipboardAPIRead&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180455345%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rMyh3WMdWjgPU3Izwd6z%2B%2BWErNXG2yga5hB1pGKZKNI%3D&reserved=0>
> /write
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromestatus.com%2Fmetrics%2Ffeature%2Fpopularity%23AsyncClipboardAPIWrite&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180455345%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jNLdXVO4lHudfzHpakMpDhsyG53CTwN9vf6uNy5SViA%3D&reserved=0>
>
> is low, we got feedback from security
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromium-review.googlesource.com%2Fc%2Fchromium%2Fsrc%2F%2B%2F3271065%2Fcomments%2F6012173d_1579d13e&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180455345%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=N0YM9O9eeikzhA8yKrMUcjKovGjHQFEG6BbIShTyJUs%3D&reserved=0>
>
> and other stakeholders
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1ha0pcpQsEgVGtPK8dd8N_0P1ynI7rXV7bR5ZFmOTD6Y%2Fedit%3Fusp%3Dsharing&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180455345%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xWiSFQfUtGEdlnSpBVfeBPdK6k1e%2B1ujLVQEPcsSpa8%3D&reserved=0>
>
> that changing the behavior of the API would break the existing sites that
> rely on the sanitization behavior and also make the API “less secure”.
> Adding an option to switch between sanitized and unsanitized HTML content
> during read, and always writing unsanitized HTML content to the system
> clipboard would address both backward compatibility and security concerns.
>
> Please let us know if you have any questions/concerns.
>
>
>
> -Anupam
>
>
>
> *From:* Thomas Steiner <to...@google.com>
> *Sent:* Tuesday, July 12, 2022 9:57 PM
> *To:* Ana Sollano Kim <ana.s...@microsoft.com>
> *Cc:* Anupam Snigdha <sni...@microsoft.com>; Bo Cupp <pc...@microsoft.com>;
> blin...@chromium.org
> *Subject:* [EXTERNAL] Re: [blink-dev] Intent to prototype: Align async
> API read/write HTML format with DataTransfer API
>
>
>
> *With the **Pickling API*
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fediting%2Fblob%2Fgh-pages%2Fdocs%2Fclipboard-pickling%2Fexplainer.md&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180455345%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fXhmmWiqMt6l6mOcV3DvemnuH1yObaUgwB10Z6nobvw%3D&reserved=0>*
>
> proposal, we will be introducing a new `unsanitized` parameter in the read
> method so the content is round trippable i.e. read would return the content
> without any sanitization.*
>
>
>
> This last part is no longer true as far as I know: the `unsanitized`
> parameter was replaced with prepending `'web '` to the MIME type. It
> doesn’t change the described round-trip behavior, just needs updating in
> the Explainer.
>
>
>
> On Wed 13. Jul 2022 at 06:24 'Ana Sollano Kim' via blink-dev <
> blin...@chromium.org> wrote:
>
> *Contact emails*
>
> anso...@microsoft.com, sni...@microsoft.com, pc...@microsoft.com
>
> *Explainer*
>
>
> https://docs.google.com/document/d/1rTEg2I-hMPXGiLrEMqKJz2Ycu6GRjlM3uvakOe84m8Q/edit?usp=sharing
>
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1rTEg2I-hMPXGiLrEMqKJz2Ycu6GRjlM3uvakOe84m8Q%2Fedit%3Fusp%3Dsharing&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180455345%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TVJ%2FRSN0NyR016aaaqai8dnH8OQVF4pa3SJREbjLoT8%3D&reserved=0>
>
> *Specification*
>
> None
>
> *Summary*
>
> This proposal aligns the HTML format read/write async API with the
> setData/getData DataTransfer APIs. Currently, when we read/write text/html
> MIME types using the async API, the sanitizer is invoked to strip out
> contents from the HTML markup due to security concerns, and styles are
> inlined in the HTML. This leads to loss of fidelity of HTML content when
> read by web authors or native apps.
>
> *Motivation*
>
> Using DataTransfer object’s setData and async clipboard write method, we
> are seeing interop differences in how the HTML content is sanitized and
> written to the clipboard. In Chromium, async clipboard write method clears
> the clipboard content first and then writes the payload which results in
> overwriting the previous HTML content that was inserted by authors using
> DataTransfer object’s setData API. It’d be beneficial for web authors if
> async clipboard and setData APIs provide the same HTML content during copy
> operation, so that round tripping is possible without any interop
> differences.
>
> Moreover, creating a fragment and inlining the styles bloats the payload
> and strips out the custom styles inserted by sites like Excel Online that
> are used to preserve excel specific semantics.
>
> *Comments*
>
> Discussion between stakeholders:
> https://docs.google.com/document/d/1ha0pcpQsEgVGtPK8dd8N_0P1ynI7rXV7bR5ZFmOTD6Y/edit?usp=sharing
>
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1ha0pcpQsEgVGtPK8dd8N_0P1ynI7rXV7bR5ZFmOTD6Y%2Fedit%3Fusp%3Dsharing&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180455345%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xWiSFQfUtGEdlnSpBVfeBPdK6k1e%2B1ujLVQEPcsSpa8%3D&reserved=0>
>
>
> Firefox's support:
> https://github.com/w3c/clipboard-apis/issues/150#issuecomment-1031684598
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fclipboard-apis%2Fissues%2F150%23issuecomment-1031684598&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180455345%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ROEVW9UURRF%2B5%2Ba8sjxc0JEhGEytl%2BkPSz%2BxYeSkz20%3D&reserved=0>
>
>
> *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=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180455345%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=HJmLbDgSNOsexZICTuhOJp8q%2FK13bIR0uQb3w8%2F4Q0U%3D&reserved=0>
>
> *TAG review*
>
>
>
> *TAG review status*
>
> As this is a Chromium specific change, we don’t believe this merits TAG
> review. But we’re happy to file a request if API_OWNERS feel this change
> should have one.
>
> *Risks*
>
>
>
> *Interoperability and Compatibility*
>
> *Gecko*: Positive
> https://github.com/w3c/clipboard-apis/issues/150#issuecomment-1031684598
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fclipboard-apis%2Fissues%2F150%23issuecomment-1031684598&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180455345%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ROEVW9UURRF%2B5%2Ba8sjxc0JEhGEytl%2BkPSz%2BxYeSkz20%3D&reserved=0>
>
>
> *WebKit*: No signal
>
> *Web developers*: Positive
>
> *Debuggability*
>
> The async clipboard APIs have basic tooling support as described in
> https://docs.google.com/document/d/1eJn5QIX4JFGackDYmdLxWXEmTDkSGj_ZGz5XY4uCKbY/edit
>
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1eJn5QIX4JFGackDYmdLxWXEmTDkSGj_ZGz5XY4uCKbY%2Fedit&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180611567%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Z%2BYstyPtwI0cfNUeEhOdgDOy2CEAET7b%2FIbXf2S5oVQ%3D&reserved=0>
>
> *Will this feature be supported on all six Blink platforms (Windows, Mac,
> Linux, Chrome OS, Android, and Android WebView)?*
>
> Yes
>
> *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=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180611567%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=AsetKCApgeMOocwukPyzE2o7ELuuGX4zxH7j4P0P08o%3D&reserved=0>
> *?*
>
> No
>
> *Flag name*
>
> TBD
>
> *Tracking bug*
>
> https://bugs.chromium.org/p/chromium/issues/detail?id=1268679
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D1268679&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180611567%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=61aSQxDgASCUZNeRKZeQawr%2BIof5q0p9%2BDsTE2Hqb%2Fw%3D&reserved=0>
>
> *Estimated milestones*
>
> No milestones specified.
>
> *Link to entry on the Chrome Platform Status*
>
> https://chromestatus.com/feature/5716132676763648
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromestatus.com%2Ffeature%2F6037871692611584&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180611567%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ayPBADdPJsAegTpPzMBjE2Xu%2FBrFU4ysCK5vwWdmsMM%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+...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/MN2PR00MB046492DBF7ABFE976B948BE8FD899%40MN2PR00MB0464.namprd00.prod.outlook.com
>
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fa%2Fchromium.org%2Fd%2Fmsgid%2Fblink-dev%2FMN2PR00MB046492DBF7ABFE976B948BE8FD899%2540MN2PR00MB0464.namprd00.prod.outlook.com%3Futm_medium%3Demail%26utm_source%3Dfooter&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180611567%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GVX0qHmpNVX69%2BJbHTvFA3c8A%2B0tSPyW%2FragEZoM%2Fn8%3D&reserved=0>
> .
>
> --
>
> Thomas Steiner, PhD—Developer Relations Engineer (https://blog.tomayac.com
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblog.tomayac.com%2F&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180611567%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WjVYfDjcXzTaXNTEzNJCIFWdwj1wf4OB1NmEKq6rqeU%3D&reserved=0>
> , https://twitter.com/tomayac
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Ftomayac&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180611567%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=D6w7eLtrYq518Gugq2TDpKV2EE8Hj4inBq8rcdCdG%2BE%3D&reserved=0>
> )
>
>
> Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fmaps%2Fsearch%2FABC-Str.%2B19%2C%2B20354%2BHamburg%2C%2BGermany%3Fentry%3Dgmail%26source%3Dg&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180611567%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=AEaylIgQgtjDEvTgEQtGKnA8jHDC76bP89ZHOLTcyaA%3D&reserved=0>
> Geschäftsführer: Paul Manicle, Liana Sebastian
> Registergericht und -nummer: Hamburg, HRB 86891
>
> ----- BEGIN PGP SIGNATURE -----
>
> Version: GnuPG v2.3.4 (GNU/Linux)
>
>
>
>
> iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom.
> hTtPs://xKcd.cOm/1181/
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fxkcd.com%2F1181%2F&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180611567%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=B8axOhXwZA6YyhzeKl4bCSS4Hg7c5QXr967mRgfAWhY%3D&reserved=0>
>
> ----- END PGP SIGNATURE -----
>
> --
>
> Thomas Steiner, PhD—Developer Relations Engineer (https://blog.tomayac.com
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblog.tomayac.com%2F&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180611567%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WjVYfDjcXzTaXNTEzNJCIFWdwj1wf4OB1NmEKq6rqeU%3D&reserved=0>
> , https://twitter.com/tomayac
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Ftomayac&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180611567%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=D6w7eLtrYq518Gugq2TDpKV2EE8Hj4inBq8rcdCdG%2BE%3D&reserved=0>
> )
>
>
> Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany
> Geschäftsführer: Paul Manicle, Liana Sebastian
> Registergericht und -nummer: Hamburg, HRB 86891
>
> ----- BEGIN PGP SIGNATURE -----
>
> Version: GnuPG v2.3.4 (GNU/Linux)
>
>
>
>
> iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom.
> hTtPs://xKcd.cOm/1181/
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fxkcd.com%2F1181%2F&data=05%7C01%7CAna.Sollano%40microsoft.com%7C61bccab639904d97a6fd08da64f7ad82%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637933312180611567%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=B8axOhXwZA6YyhzeKl4bCSS4Hg7c5QXr967mRgfAWhY%3D&reserved=0>
>
> ----- END PGP SIGNATURE -----
>
--
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/6a07618e-e113-40d2-94d0-c090765fe9d2n%40chromium.org.
