Contact emails sni...@microsoft.com<mailto:sni...@microsoft.com>, sa...@microsoft.com<mailto:sa...@microsoft.com>, est...@chromium.org<mailto:est...@chromium.org>, jsb...@chromium.org<mailto:jsb...@chromium.org>, asu...@chromium.org<mailto:asu...@chromium.org>
Explainer https://github.com/w3c/clipboard-apis/issues/170 Specification https://w3c.github.io/clipboard-apis/#clipboard-item-interface https://w3c.github.io/clipboard-apis/#dom-clipboarditem-supports Summary Currently during async clipboard write operation, there is no way for the web authors to detect if a particular mime type is supported by the UAs or not before attempting to actually write the formats to the clipboard. This not only affects developer ergonomics as now web authors have to attempt to write to the clipboard first in order to find out whether write failed due to a particular mime type not supported by the UAs (or sometimes add version checks that are unreliable at best), but also leads to unnecessary cost in terms of CPU cycles, COGS etc in order to produce an expensive web custom format which may not be supported by a particular browser. Blink component Blink>DataTransfer<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EDataTransfer> Search tags asyncclipboard<https://chromestatus.com/features#tags:asyncclipboard> TAG review None TAG review status Not applicable WebFeature UseCounter name kAsyncClipboardAPISupportsTypes Risks Interoperability and Compatibility None Gecko: Positive (https://github.com/w3c/clipboard-apis/issues/170#issuecomment-1064240391) WebKit: Positive (https://github.com/w3c/clipboard-apis/issues/170#issuecomment-1064240391) Web developers: Strongly positive (https://github.com/w3c/clipboard-apis/issues/165#issuecomment-1197976360) Multiple Github issues were filed for this feature: https://github.com/w3c/clipboard-apis/issues/165#issuecomment-1197976360 https://github.com/w3c/clipboard-apis/issues/67#issuecomment-650439507 https://github.com/w3c/clipboard-apis/issues/170 Other signals: Ergonomics N/A Activation N/A Security N/A WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? N/A Debuggability Existing devtools support should be sufficient to query the static method from ClipboardItem. 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://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>? Yes Flag name on chrome://flags ClipboardSupportedTypes Finch feature name None Non-finch justification None Requires code in //chrome? False Tracking bug https://bugs.chromium.org/p/chromium/issues/detail?id=1483026 Measurement Added usage metrics: AsyncClipboardAPISupportsTypes Adoption expectation Excel online is ready to use this API for adding web custom format support. Adoption plan Support for web custom format is already in inner rings, so once this gets added to the clipboard API, Excel would be ready to use it right away. Sample links https://lake-cobalt-way.glitch.me<https://lake-cobalt-way.glitch.me/> Estimated milestones Shipping on desktop 119 DevTrial on desktop 119 Shipping on Android 119 DevTrial on Android 119 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5176417696612352 This intent message was generated by Chrome Platform Status<https://chromestatus.com/>. Thanks, Anupam Sent from Outlook<http://aka.ms/weboutlook> -- 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/BY5PR00MB08403037ADC9DD9A11BB4603CFFBA%40BY5PR00MB0840.namprd00.prod.outlook.com.
