Re: [webauthn] preventSilentAccess() -- what effect does calling it have?

The danger with allowing "undefined behavior" or "methods that do nothing now, but will do things in the future" in the spec is the following: People may build libraries/websites that do the right thing now, but will break when we update the API to have behavior where things are currently NOOPs

-- 
GitHub Notification of comment by leshi
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/565#issuecomment-339414842 using your GitHub account

Received on Wednesday, 25 October 2017 17:52:11 UTC