- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Mar 2020 14:05:41 +0000
- To: public-webrtc@w3.org
foolip has just created a new issue for https://github.com/w3c/webrtc-extensions: == "return undefined" when populating a dictionary member is unclear == "Otherwise, return undefined" is used in two places: https://w3c.github.io/webrtc-extensions/#dom-rtcrtpcontributingsource-capturetimestamp https://w3c.github.io/webrtc-extensions/#dom-rtcrtpcontributingsource-sendercapturetimeoffset If one takes this literally, one would create an own property with the value undefined. However, the intended behavior is almost certainly to not add the member at all. Aside: undefined is a JS type/value, where void is the IDL type. The IDL type "can only be used as the return type of an operation or the parameter of a promise type" (https://heycam.github.io/webidl/#idl-void) so there actually isn't a way to do express the IDL dictionary equivalent of `{ something: undefined }`. Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/34 using your GitHub account
Received on Wednesday, 11 March 2020 14:05:43 UTC