Re: [w3c/editing] Explicitly define supported MIME types in Async Clipboard Spec (#305)

> My understanding was that specs were supposed to be written to ensure APIs can be flexible and future-proof, potentially including things that aren't yet implemented in all browsers, but I understand that this can make them confusing for interoperability.

I think that could be achieved by that browsers MAY support those types. But we really need to say MUST for the types that all browsers support.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/305#issuecomment-843635197