Thanks Florian for your thoughts on this! > We have a few open issues on the spec. > https://github.com/w3c/csswg-drafts/labels/css-highlight-api-1<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fcsswg-drafts%2Flabels%2Fcss-highlight-api-1&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086310969%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=kOB6Y3bLCEaYvmAwr%2BjZmgm9FeF%2ByR5uxTM2WSBcRWA%3D&reserved=0>
Makes sense, we'll work on driving down these issues in CSSWG before shipping, and we'll make sure that we have at least a clearer plan regarding accessibility for the API. I'll update this thread when more progress has been made here. > The custom highlights defined by this API are highlights, as defined in > https://drafts.csswg.org/css-pseudo-4/#highlight-pseudos<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrafts.csswg.org%2Fcss-pseudo-4%2F%23highlight-pseudos&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086330959%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=BVOmsUayTL3qxgka8VSBDABT%2BmxAfv%2BUHpORvSCK5Kg%3D&reserved=0>, > and Chrome's current behavior is actually far from spec compliant here. Our thinking on this is that this first version of the Highlight API is mainly useful for scenarios like custom find-on-page where highlights use simple formatting (like background-color and color), and overlapping highlight ranges are not common. So, we don't expect the discrepancies between the Chromium implementation and the highlight pseudos specs to be a big issue. For example, many of these longstanding highlight painting issues exist with the browser's current find-on-page implementation, but in practice they are minimally disruptive. So our thinking is that fixing these highlight painting issues in the future would not cause significant breakage for sites built using the current capabilities of the API. Thus I'm hesitant to conclude that this reworking of the highlight painting code should be a blocker for shipping the API. From: Florian Rivoal <[email protected]> Sent: Friday, August 13, 2021 2:32 PM To: Daniel Clark <[email protected]> Cc: [email protected]; Fernando Fiori <[email protected]>; Bo Cupp <[email protected]>; Sanket Joshi (EDGE) <[email protected]>; Delan Azabani <[email protected]> Subject: Re: [blink-dev] Intent to Ship: Custom Highlight API Hi all! Being one of the co-editors of this spec, I'm super happy about this getting traction... but I think shipping is a little bit premature: * We have a few open issues on the spec. https://github.com/w3c/csswg-drafts/labels/css-highlight-api-1<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fcsswg-drafts%2Flabels%2Fcss-highlight-api-1&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086310969%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=kOB6Y3bLCEaYvmAwr%2BjZmgm9FeF%2ByR5uxTM2WSBcRWA%3D&reserved=0> Most of them should be pretty easy, and I'm happy to prioritize them. It seems better to get the API / behavior to be stable and then ship rather than the other way around. * One of the open issues is possibly not easy, but important: it has not yet been determined how this was supposed to work with screen-readers and other assistive technologies. I think this ought to be given serious thoughts, and probably should be solved before shipping https://github.com/w3c/csswg-drafts/issues/6498<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fcsswg-drafts%2Fissues%2F6498&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086320974%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Z66L%2B19E5Pyg9UZbTyKMAs9xSuoatkoBlVOZbECKxX4%3D&reserved=0> / https://github.com/w3c/csswg-drafts/issues/4601<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fcsswg-drafts%2Fissues%2F4601&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086330959%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6hi9DlbJQ9IjrqE95nNcSYMLyiW%2B84jbIDNv8IKaBgI%3D&reserved=0> * The custom highlights defined by this API are highlights, as defined in https://drafts.csswg.org/css-pseudo-4/#highlight-pseudos<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrafts.csswg.org%2Fcss-pseudo-4%2F%23highlight-pseudos&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086330959%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=BVOmsUayTL3qxgka8VSBDABT%2BmxAfv%2BUHpORvSCK5Kg%3D&reserved=0>, and Chrome's current behavior is actually far from spec compliant here. Luckily, this is in the process of being fixed, but shipping custom highights before landing those fixes risks causing a compat problem: if people start to use custom highlight with the current/broken cascading and painting model, and then we fix it, that's liable to cause plenty of annoyances. As long as fixing those is considered a dependency for this intent to ship, then that's great, but shipping the API first and fixing the behavior later is maybe not so great. See at least https://bugs.chromium.org/p/chromium/issues/detail?id=1147859<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D1147859&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086340952%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lQWB%2FvbcX0GUimfT4CwFe%2BvBFLiVcKzme78BLySAie0%3D&reserved=0> -Florian On Aug 12, 2021, at 23:23, 'Daniel Clark' via blink-dev <[email protected]<mailto:[email protected]>> wrote: Contact emails [email protected]<mailto:[email protected]>, [email protected]<mailto:[email protected]>, [email protected]<mailto:[email protected]>, [email protected]<mailto:[email protected]> Explainer https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/highlight/explainer.md<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftEdge%2FMSEdgeExplainers%2Fblob%2Fmain%2Fhighlight%2Fexplainer.md&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086340952%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=BpzVAw9s7%2Fc7r%2BZo1zrrqbw34TzgL4VkT8KovB3qdlk%3D&reserved=0> Specification https://drafts.csswg.org/css-highlight-api-1/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrafts.csswg.org%2Fcss-highlight-api-1%2F&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086350965%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=dWllFXbxdi%2FtANEnHxFEPNymFkyUpzuWcOuFCDOnw9A%3D&reserved=0> Summary The custom highlight API provides a way for web developers to style the text of arbitrary ranges. This is useful in a variety of scenarios, including editing frameworks that wish to implement their own selection, find-on-page over virtualized documents, multiple selections to represent online collaboration, or spellchecking frameworks. Blink component Blink>Editing<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Flist%3Fq%3Dcomponent%3ABlink%253EEditing&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086350965%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9Z6rW9escgxsGZSKu5yHFNLeGoRf1t2aXIG1jgGLo5w%3D&reserved=0> Search tags Custom Highlight API<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromestatus.com%2Ffeatures%23tags%3ACustom%2520Highlight%2520API&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086360963%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qOgkLXG16y36NEK8hH11WvX4bT56so%2FGSZ1bOA%2Bhimo%3D&reserved=0>, Highlight API<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromestatus.com%2Ffeatures%23tags%3AHighlight%2520API&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086360963%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=UkupBjpTl4YUA0Hd4LEgKCkBdoh4%2F%2BpB2AXx0BH2AKo%3D&reserved=0> TAG review https://github.com/w3ctag/design-reviews/issues/584<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3ctag%2Fdesign-reviews%2Fissues%2F584&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086370959%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5qDR3CruTm%2FC8gsJoFbb%2F3JCUEMWx0F2MNCr4FHwL%2FI%3D&reserved=0> TAG review status Issues addressed Risks Interoperability and Compatibility Low: This feature received positive support from Safari and Firefox at TPAC 2019. Safari has implemented the feature. Gecko: No signal (https://github.com/mozilla/standards-positions/issues/482<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromestatus.com%2Fadmin%2Ffeatures%2Flaunch%2F5436441440026624%2F5%3Fintent%3D1&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086370959%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=coXvK%2Bkl7ms%2FdetboB0BfwRysXOZ9A8U%2Bi1scJkB%2Fjw%3D&reserved=0>) WebKit: Shipped/Shipping (https://developer.apple.com/safari/technology-preview/release-notes/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper.apple.com%2Fsafari%2Ftechnology-preview%2Frelease-notes%2F&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086380934%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=0VNuGq43zSAkmTICOrED7Rli9%2BHCgJ%2BMyw7ubIpFuiw%3D&reserved=0>) Highlight API listed in Release 99 notes. Web developers: Strongly positive (https://github.com/w3c/csswg-drafts/issues/4307<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fcsswg-drafts%2Fissues%2F4307&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086380934%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xAIN5akPOP%2Bcn%2BcyLQRPfkqp0I0M7MP2yRgRYi5CRxE%3D&reserved=0>) Multiple use cases have been pointed out in this issue. CKEditor has also shown support from the first highlight API explainer. Ergonomics The highlight API will be the first use case for constructible StaticRanges, which the API permits as an alternative to Iive Ranges because they do not incur cost during DOM mutations. Activation No. Web developers should be able to use the feature as-is. It is also easy to feature detect (checking for the existence of CSS.highlights). Debuggability DevTools shows ::highlight pseudo elements, in the same way that it shows other pseudo elements. 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%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086390943%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xXjGRQhBwOA9MH4prlIN2%2B0B5%2FlmIXeoWqNyPrIa724%3D&reserved=0>? Yes https://wpt.fyi/results/css/css-highlight-api?label=master&label=experimental&aligned&q=css<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwpt.fyi%2Fresults%2Fcss%2Fcss-highlight-api%3Flabel%3Dmaster%26label%3Dexperimental%26aligned%26q%3Dcss&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086390943%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1Frgh1tzbcOvJUPkeTrAvxA6R1C1bCVNzO570gjmYo4%3D&reserved=0> https://wpt.fyi/results/css/css-highlight-api/painting?label=master&label=experimental&aligned&q=css<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwpt.fyi%2Fresults%2Fcss%2Fcss-highlight-api%2Fpainting%3Flabel%3Dmaster%26label%3Dexperimental%26aligned%26q%3Dcss&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086400921%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=V%2FFj1jGsGmEMj4XKxUyQfqx5PrHIwqtZAekjAmH4svU%3D&reserved=0> Flag name --enable-blink-features=HighlightAPI Requires code in //chrome? False Tracking bug https://crbug.com/1164461<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcrbug.com%2F1164461&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086400921%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=8Y4m%2BwMLKQev07tHyWZdJjgElap5u5eEfs2RxfUtQGg%3D&reserved=0> Estimated milestones Comments: Highlight API does not yet support all of the pseudos at https://www.w3.org/TR/css-pseudo-4/#highlight-styling<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fcss-pseudo-4%2F%23highlight-styling&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086410912%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qxgNWcbTbaknvW%2FjYrMExjNs5iYKkqRLlNaWRClCnF0%3D&reserved=0> -- the current implementation only supports color and background-color. However, we believe there is value in shipping starting with just these styles, since they are sufficient to support key scenarios like custom find-on-page. Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5436441440026624<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchromestatus.com%2Ffeature%2F5436441440026624&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086410912%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=UPEKE8WHTkx8u1alX0PHBvx0O86xsXbRfsTFo2Nyslw%3D&reserved=0> Links to previous Intent discussions Intent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/Ix2u8NHG5Po/m/jjMjWIHXAQAJ<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fa%2Fchromium.org%2Fg%2Fblink-dev%2Fc%2FIx2u8NHG5Po%2Fm%2FjjMjWIHXAQAJ&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086420909%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=XCEhmZ%2FCkwm2zoHpP0Q31ZGwdMxp3zmrhgSvKbQ34so%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%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086420909%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hcFCNzgUDTBvsD2sE36sq9LNIfS7q2ky4WNbVGV30W8%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]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/BL0PR00MB0435222C2F1E0F4BC013388FC5F99%40BL0PR00MB0435.namprd00.prod.outlook.com<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fa%2Fchromium.org%2Fd%2Fmsgid%2Fblink-dev%2FBL0PR00MB0435222C2F1E0F4BC013388FC5F99%2540BL0PR00MB0435.namprd00.prod.outlook.com%3Futm_medium%3Demail%26utm_source%3Dfooter&data=04%7C01%7Cdaniec%40microsoft.com%7C6113ef857bf7463196a308d95ea1bf59%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637644871086420909%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=x9TvHCgbeQM6lDf3XDM4QqtBPIGpw0uDRkJcZue373Y%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/MW2PR00MB04411C67E229EF0081041C59C5FE9%40MW2PR00MB0441.namprd00.prod.outlook.com.
