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

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

I suppose it is the case that the part after `'web '` has to be a valid MIME type. I missed that detail because it's not mentioned under [optional data types](https://w3c.github.io/clipboard-apis/#optional-data-types-x). Perhaps that section should be updated to indicate that the prefix alone is not sufficient, and there are requirements for the rest of the string/type?

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

Which of [these](https://github.com/w3c/clipboard-apis/pull/192#issuecomment-1726703751) should return true?

The reason I questioned the utility of `supports('web image/foo')` is because, as far as I understood, everything after the `'web'` prefix didn't matter. If the API accepts full custom types like `web text/richtext`, that suggests a user agent might return a different value for one full custom type vs another, but if the implementation is "just check the first 4 characters" then that's a false impression. Given that the suffix does at least have to be a valid MIME type (`'web foo/bar'`) should return false, it does matter a little bit so it does make more sense to me that the API can take full custom types.

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

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