- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Dec 2017 09:17:18 +0000
- To: public-webrtc-logs@w3.org
There are 4 cases here: - Header extension (RFC 6464) parsing not implemented - Header extension doesn't exist on this particular packet - Header extension exist with V flag value "false" - Header extension exists with V flag value "true" The second case isn't "the browser is not providing the information", it is "the browser is telling us that the packet does not provide this information". This maps to "missing", "null", "false" and "true". We could have other mappings, but we need all 4 states to be representable. It's an advantage (to my mind) that browsers that implemented this API before this particular piece was cooked up (I don't think there were any, but the principle is good) will be compatible with the specification by omitting the member. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1689#issuecomment-351652929 using your GitHub account
Received on Thursday, 14 December 2017 09:17:20 UTC