[w3ctag/design-reviews] Feature detection for supported clipboard formats (Issue #901)

こんにちは TAG-さん!

I'm requesting a TAG review of Feature detection for supported clipboard formats.

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.

  - Explainer¹ : https://github.com/w3c/clipboard-apis/issues/170
  - Specification URL: https://w3c.github.io/clipboard-apis/#dom-clipboarditem-supports, https://w3c.github.io/clipboard-apis/#clipboard-item-interface
  - Tests: https://github.com/web-platform-tests/wpt/pull/41993
  - User research: N/A
  - Security and Privacy self-review²: N/A
  - GitHub repo (if you prefer feedback filed there): https://github.com/w3c/clipboard-apis/issues
  - Primary contacts (and their relationship to the specification):
      - Anupam Snigdha (@snianu), Microsoft, Sanket Joshi (@sanketj), Microsoft
  - Organization(s)/project(s) driving the specification: EditingWG
  - Key pieces of existing multi-stakeholder review or discussion of this specification: https://github.com/w3c/clipboard-apis/issues/170
  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5176417696612352

Further details:

  - [X] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - Relevant time constraints or deadlines: We're planning to ship this in Chrome 119.
  - The group where the work on this specification is currently being done: This API was approved by the EditingWG
  - The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): EditingWG
  - Major unresolved issues with or opposition to this specification: None
  - This work is being funded by: Microsoft

You should also know that...

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: 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

We'd prefer the TAG provide feedback as (please delete all but the desired option):

  ☂️ open a single issue in our GitHub repo **for the entire review**



-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/901
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/901@github.com>