Re: [heycam/webidl] clearly state that declared interface members must be present on objects implementing the interface (#770)

thanks, Domenic, for the underlying details.

Well, the issue we've had at least one instance of recently, is that a browser developer didn't understand that interface members are required by definition (is that uniformly the case?), and they were returning an  [AuthenticatorAssertionResponse](https://www.w3.org/TR/webauthn/#authenticatorassertionresponse) lacking a `userHandle` property, rather than returning the attribute with a `null` value. And thus upon returning said object to webauthn relying parties, some were choking and some were not... 

I was simply groveling thu the WebIDL spec for a clear definitive statement saying "declared interface members must be present (i.e., as "accessible properties") on objects implementing an interface", or "interface members must be present", or something clear that a non-WebIDL expert can understand without poring thru the WebIDL spec. I wish to reference such a statement from the WebAuthn spec. Presently, I suppose we can add a Note: to the  WebAuthn spec saying "Members of the interfaces defined in this are required to be present by definition, see [[WebIDL]] (or just trust us)".

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/770#issuecomment-522735278