Thanks, it'd be interesting to hear from the security researchers that found the original flaws if that is indeed sufficient. I also think that the specification should define the maximum allowed frequency to ensure end user security and interoperability. (There's some text on this, but it's not specific.) Also, what is the plan for the various legacy APIs in this area? Is the hope that those can be removed somehow? Are there metrics to back that up? Or will we end up with duplicate API surface? -- 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/207#issuecomment-351369928
Received on Wednesday, 13 December 2017 11:54:28 UTC