Re: [webauthn] Revise same-origin as ancestor requirements

Not putting this in the spec until L2 means that certain relying party use cases (which seem to be important for adoption) won't be implementable for at least a year.

Any chance we could do this for L1?

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

Received on Wednesday, 18 July 2018 17:54:29 UTC