Interesting proposal! Wondering why the TAG review is marked as pending when there was no review submitted?
On 2023年03月04日 10時19分16秒 (+09:00), Joshua Bell wrote: Hey folks! This is very exciting to see. I notice the linked explainer is marked Archived, and links to itself as the current version? The attached design doc is helpful, but unhelpfully forbids copy/paste. Can you fix that? The explainer calls out that there's no API change, but the design doc's example shows the ClipboardItem consuming what looks like a promise that resolves to a function... which doesn't seem to be what's intended. What's the best way for other Chromium folks to help you iterate on the explainer and API design, and provide feedback on the design doc? Again, this is awesome to see - I've definitely heard requests for this functionality from many partners. On Fri, Mar 3, 2023 at 3:48 PM 'Ana Sollano Kim' via blink-dev <[email protected]> wrote: Sending some clarifications. TAG review Performance improvement. No change in Web APIs. TAG review status Not applicable Interoperability and Compatibility Chromium is the first browser to support delayed clipboard rendering. Firefox and Safari have expressed no concerns about the concept. Gecko: Neutral (https://github.com/mozilla/standards-positions/issues/758) Expressed no concerns, conversation: https://github.com/w3c/editing/issues/417#issuecomment-1452770119 WebKit: Positive (https://github.com/WebKit/standards-positions/issues/144) Expressed no concerns, conversation: https://github.com/w3c/editing/issues/417#issuecomment-1452770119 Web developers: Positive Our partners have shown interest to leverage delayed clipboard rendering along with the Clipboard Async API's custom formats. 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? No. Design Doc https://docs.google.com/document/d/1OIyzmilYbV7xc6JvNt73ELQX_DyiL-b3tkFZ3OGBrt0/edit?usp=sharing From: Ana Sollano Kim Sent: Friday, March 3, 2023 1:22 PM To: [email protected]; Anupam Snigdha <[email protected]>; Sanket Joshi (EDGE) <[email protected]>; '[email protected]' <[email protected]>; '[email protected]' <[email protected]>; '[email protected]' <[email protected]>; '[email protected]' <[email protected]>; '[email protected]' <[email protected]> Subject: Intent to Prototype: Delayed clipboard rendering Contact emails [email protected], [email protected], [email protected] Explainer https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/DelayedClipboard/DelayedClipboardRenderingExplainer.md Specification https://w3c.github.io/clipboard-apis Summary Delays the generation of the clipboard payload until it is needed by the target applications. Delayed clipboard rendering leverages the existing Async Clipboard API to allow web applications to improve performance when exchanging large data payloads by only producing the clipboard payload once a target application attempt to access it. Blink component Blink>DataTransfer Motivation Source applications typically don’t know where the user intends to paste the content at the time of copy, so web applications may produce several formats when writing to the clipboard to prepare for many possible target applications. The generation of one or more representations may take enough time that it is noticeable to the user, but it is unlikely that the target application will need all produced representations. Initial public proposal https://github.com/w3c/editing/issues/417 TAG review TAG review status Pending Risks Interoperability and Compatibility Chromium is the first browser to support delayed clipboard rendering. Firefox and Safari have expressed no concerns about the concept. Gecko: No signal (https://github.com/w3c/editing/issues/417#issuecomment-1452770119) Expressed no concerns. WebKit: No signal (https://github.com/w3c/editing/issues/417#issuecomment-1452770119) Expressed no concerns. Web developers: No signals Other signals: 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? Debuggability The Async Clipboard API have tooling support as described in the DevTools support checklist. Is this feature fully tested by web-platform-tests? No Flag name TBD Requires code in //chrome? False Tracking bug https://bugs.chromium.org/p/chromium/issues/detail?id=1408850 Estimated milestones No milestones specified Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5124936324087808 This intent message was generated by Chrome Platform Status. -- 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/DM5PR00MB0328BDEAEA01D55DFB967AD0FDB39%40DM5PR00MB0328.namprd00.prod.outlook.com. -- 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/CAD649j6Cz4fUEbAK%3DRJ7to0PJ0Qp72OcSw-Au_vQZdRTS%2BC6%2Bw%40mail.gmail.com. -- 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/1678044230952.1197925597.3289764502%40chromium.org.
