- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 30 Sep 2022 15:49:09 +0000
- To: public-webrtc-logs@w3.org
> For new APIs we don't want undefined and null to mean the same thing.
That's interesting. Can you please link to support for this advice? I couldn't find it in the design guidelines.
> That typically results in null throwing, just like any other unsupported type would.
Even for object and interface inputs? E.g. we want the following to reject?
```js
let controller = null;
button.onclick = async () => {
await navigator.mediaDevices.getDisplayMedia({controller}); // TypeError ?
}
```
I'm no fan of `null` personally, but I wasn't aware we'd gotten there yet.
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/236#issuecomment-1263739889 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 30 September 2022 15:49:11 UTC