- From: cynthia <notifications@github.com>
- Date: Mon, 09 Sep 2019 23:27:07 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 10 September 2019 06:27:29 UTC
Sorry for the extremely delayed reply - this issue fell through the cracks and we did not notice that there was an update. One other bit we are curious about is if there was positive signals from other implementors on this feature. > The most important feedback to me would around ensure that the proposed API is consistent with the fundamental Web architecture and specifically with the existing device APIs that you all have seen. > Specifics are good here. I have outlined a number of concerns I had and how we addressed them. What are you concerned about specifically? We're drafting this right now, will post shortly after this comment. > Is that new? I don't think we filled one out for the Bluetooth gatt connection API. Somewhat - I'm not sure when this spec was filed, but it is now a mandate in our new review process. We understand it is a bit of extra work, but a self-review is an extremely useful starting point for us to look into the potential privacy/security implications from the new feature. -- 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/333#issuecomment-529790475
Received on Tuesday, 10 September 2019 06:27:29 UTC