- From: L. David Baron <notifications@github.com>
- Date: Tue, 11 Jun 2019 21:56:35 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 12 June 2019 04:56:57 UTC
Those appear to cover the entirety of WebAuthn, not the particular issue the TAG is being asked to review here. Is there something covering just that? Some questions that I might expect an [explainer](https://w3ctag.github.io/explainers) about the feature detection (in addition to what's in the Background section [above](https://github.com/w3ctag/design-reviews/issues/383#issue-453252779)) to answer might be: * what led to the choice of the level of granularity chosen, and what alternatives were considered * how the set of features exposed corresponds to the API surface (because separating the feature detection from the API surface is often undesirable) * what the major points of disagreement about the design were (and the arguments for each) -- 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/383#issuecomment-501120440
Received on Wednesday, 12 June 2019 04:56:57 UTC