Re: [w3ctag/design-reviews] Autoplay Detection API (#356)

This was [discussed](https://github.com/w3ctag/meetings/blob/gh-pages/2019/telcons/04-24-minutes.md#autoplay-detection-api---hober-hadleybeeman) in yesterday's teleconference.

I think one of the conclusions is that our template for requesting TAG reviews is better suited for specifications that already have consensus within the group working on them, than for areas with active disputes.  It also wasn't clear to what extent the review request was (a) a request to review one of the two alternatives (b) a request to review both alternatives, or (c) a request to weigh in on the dispute between the alternatives.  If it's (c), then we'd be hesitant to weigh in without a chance to read the arguments presented by each side in that dispute... and it's not entirely clear where those are.

In addition to the sync vs. async question, I also raised a question about having a document-level API versus an element-level API if the answer is only consistent across all elements in some browsers.

-- 
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/356#issuecomment-486461058