Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240)

ashishkum-ms left a comment (w3c/clipboard-apis#240)

@annevk, thank you for your suggestion to consider adding new `readTypes` like api.
I think a separate `readTypes` API could offer some discoverability benefits (due to autocomplete in console when dev types navigator.clipboard.read..). But after reviewing, the benefits of extending the current `read` API with a `types` argument seem to 
outweigh.
Extending the current `read` API with `types` argument:
1) Avoids introducing new overlapping API, since options like unsanitized data would need to be maintained across both APIs. 
This could mean maintaining two APIs that do pretty much same things. This may lead to increased maintenance overhead for user agents and the specification, particularly as new options are introduced in future.
And that maintaining a single, API helps keep the platform simpler and more consistent for developers.

Looking forward to your further thoughts on this and open to feedback.

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

Message ID: <w3c/clipboard-apis/issues/240/3248221337@github.com>