Re: [w3ctag/design-reviews] Contact API (#337)

Hi @torgo. Sorry for the miscommunication, I thought the issues raised had been resolved. 

To reply directly to @dbaron's points

- #337 (comment) raising the issue of how this differs from previous contacts proposals
There's an entire section in the explainer dedicated to previous attempts, some context around them, and how this proposal differs: https://github.com/WICG/contact-api#previous-standardization-attempts

- risks of abuse, which seems to have led to updates to the explainer
The explainer has also been updated to cover the points brought up.

- `<input type=contact>` alternative
Although I agree this has some benefits, and could work nicely in conjunction with the JS API, it still has some shortcomings as discussed in the thread above, and in the [explainer](https://github.com/WICG/contact-api#previous-standardization-attempts). Considering it's more of a "nice-to-have" alternative than anything, I'm a bit hesitant to include it in the proposal unless there are signs of developer/implementer interest.

> Is there a venue for this work beyond WICG? Is there any signal of multiple implementation at this point?

There are no signs of multiple implementation yet, which is why it's still in the WICG. This is something we can get more clarity on during the upcoming TPAC.

Thanks!


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