Feature detection for supported clipboard formats

[snianu]

WebKittens

@annevk @whsieh

Title of the spec

Feature detection for supported clipboard formats

URL to the spec

https://w3c.github.io/clipboard-apis/#clipboard-item-interface, https://w3c.github.io/clipboard-apis/#dom-clipboarditem-supports

URL to the spec's repository

https://w3c.github.io/clipboard-apis/#clipboard-item-interface, https://w3c.github.io/clipboard-apis/#dom-clipboarditem-supports

Issue Tracker URL

w3c/clipboard-apis#170

Explainer URL

w3c/clipboard-apis#170

TAG Design Review URL

w3ctag/design-reviews#901

Mozilla standards-positions issue URL

mozilla/standards-positions#889

WebKit Bugzilla URL

https://bugs.webkit.org/show_bug.cgi?id=279712

Radar URL

No response

Description

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.

Note that this was discussed in the EditingWG meeting and was approved by representatives from Webkit, FF & Chromium: https://www.w3.org/2022/04/14-editing-minutes.html#r01

Positive signal from Gecko: w3c/clipboard-apis#170 (comment)
Web developers: Strongly positive (w3c/clipboard-apis#165 (comment))
Multiple Github issues were filed for this feature: w3c/clipboard-apis#165 (comment) w3c/clipboard-apis#67 (comment) w3c/clipboard-apis#170

[marcoscaceres]

Discussed this internally with colleagues and, unless anyone objects within a week, we are inclined to label this as "support".

[annevk]

It's not clear how this algorithm ends up working for optional data types. I filed w3c/clipboard-apis#200 on that.

[karlcow]

https://bugs.webkit.org/show_bug.cgi?id=279712