- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Dec 2020 09:04:37 +0000
- To: public-webrtc-logs@w3.org
> True, though I don't think this impacts interpretation, since specs are written for implementers, not users. And following it leads us here. We could add a second note saying we messed up, and here's a workaround. Following it leads us here, but only after several editors and implementers discussing ways to avoid what I think is a less desirable but more straight-forward interpretation, which would be to have getCapabilities() block JS and always expose the same capabilities (HW or SW, known after block). It would even be more useful, but also taboo. Even with our note this is still a valid interpretation and having to do said workaround is not clear even to implementers. But I say let's follow-up in https://github.com/w3c/webrtc-extensions/issues/57, for now the note serves as a "heads up, there be dragons here". -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2617#issuecomment-745953704 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 December 2020 09:04:38 UTC