On Wed, Sep 29, 2021 at 3:02 AM 'Anupam Snigdha' via blink-dev < blink-dev@chromium.org> wrote:
> Contact emails > > sni...@microsoft.com, m...@chromium.org > > > Explainer > > https://www.w3.org/TR/clipboard-apis/#typedefdef-clipboarditemdata > That's not really an explainer. Can you expand on what this method does, how would the new method look like and how would developers use it? > > > > Specification > > https://www.w3.org/TR/clipboard-apis/#typedefdef-clipboarditemdata > > > Summary > > Add promise support to `ClipboardItem` object. This helps the web author > to call async clipboard write method without having to provide the Blob > data synchronously. Authors can choose to resolve the promise later when > the Blob data is available. > > Blink component > > Blink>DataTransfer > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EDataTransfer> > > TAG review > > N/A. The spec is in Working Draft state and has already been shipped by > Apple. > Was this change discussed in a standards venue? > > TAG review status > > Not applicable > > Risks > > None. Currently the API takes in a Blob type and the promise to a Blob > would resolve implicitly which wouldn’t require any changes nor would it > break any existing sites. > > Is there compat risk here? Are developers already using the non-Promise method? What is it returning today? What should adoption patterns to avoid risks in non-supporting browsers? Interoperability and Compatibility > > > *Gecko*: In Development( > https://bugzilla.mozilla.org/show_bug.cgi?id=1619947) > It's not clear what this issue actually implements. Did they already implement and ship the Promise based API? If not, it'd be good to ask for official signals: https://bit.ly/blink-signals > > *WebKit*: Shipped > > *Web developers*: Positive ( > https://bugs.chromium.org/p/chromium/issues/detail?id=1014310). This is > also a highly requested feature by MS Office products. > > Debuggability > > The async clipboard APIs have basic tooling support as described in this > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1eJn5QIX4JFGackDYmdLxWXEmTDkSGj_ZGz5XY4uCKbY%2Fedit&data=04%7C01%7Csnianu%40microsoft.com%7Cde1bc8a46a3b4120b59208d9585fc842%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637637990693775265%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=dSuOosp8dhfpjAxZugueRGooEU0BSrXgii3BUhDPXgM%3D&reserved=0> > doc. > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> > ? > > Yes > > Flag name > > None. > > Requires code in //chrome? > > False > > Tracking bug > > https://bugs.chromium.org/p/chromium/issues/detail?id=1014310 > > Estimated milestones > > 96 > > Link to entry on the Chrome Platform Status > > https://www.chromestatus.com/feature/5733949474078720 > > This intent message was generated by Chrome Platform Status > <https://www.chromestatus.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 blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/SN6PR00MB0397C14B0F073635A96B475ACFA99%40SN6PR00MB0397.namprd00.prod.outlook.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/SN6PR00MB0397C14B0F073635A96B475ACFA99%40SN6PR00MB0397.namprd00.prod.outlook.com?utm_medium=email&utm_source=footer> > . > -- 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/CAL5BFfWDagU1wM19JPod0JPVMttLxjE273aRoD_Yhp5ZM6csXA%40mail.gmail.com.
