Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)

I don't have strong feelings here, but my intuition for how developers would try to use supports() for custom types in practice is either:

* `ClipboardItem.supports('web valid/type');` // where we'd return true for 'web' + space prefix and valid mime type suffix suffix
* `ClipboardItem.supports('web');` // true

The former aligns with the concept of supports() being a way of testing what the ClipboardItem constructor would do without wasting time, but accepting 'web' on its own seems like a nice to have. 

'web ' (web + space, with no suffix) on its own isn't accepted by https://w3c.github.io/clipboard-apis/#dom-clipboarditem-clipboarditem so far as I can tell (maybe I'm wrong?), and it's not intuitive to me that a developer would try it.

But maybe I'm missing the point of the discussion. What are the alternatives we're considering?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/clipboard-apis/pull/192#issuecomment-1753661815
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/clipboard-apis/pull/192/c1753661815@github.com>