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

@annevk 
No strong opinion here. A string argument and a dictionary overload makes total sense if a) the string argument is the "primary" criteria for testing, and b) its meaning is clear when you see function calls in the wild. If you don't envision any other conceivable criteria for testing in the near or medium term future, that would indicate that MIME type might fall in that category. I have some reservations about (b) for the custom types, but they’re not super strong.

@snianu 
> Note that this review was opened in September 2023 and we waited couple of months for feedback. Just for my understanding, in the future, should we close the issue if we ship it in one or more browsers? Is there a specific tag that I need to be aware of in the issue that indicates that it is in-review and we should wait for feedback?

There is no such tag because reviews happen quite fast, most of the (unfortunately long) wait time is review requests waiting in the queue. You can however follow the milestones, which indicate when we plan to get to it.
If an API is about to ship, ideally, you should ping us so we could bump it in the queue.
But if an API has shipped and reviewing would not make a difference any more, yes, I would recommend closing it (or ping us, so we can close it with the right label: timed out) so we can reallocate these resources to reviews where reviewing *would* actually make a difference.

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

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