- From: Nick Doty via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Apr 2018 20:03:59 +0000
- To: public-media-capture-logs@w3.org
> Those are informational for developers but they are not offered to the JS, i.e. a hardware accelerated version is only supported if and where there's a software fallback, and a positive response to isTypeSupported() is not enough to differentiate among them. Is that intended to be a requirement? If so, that would definitely mitigate privacy concerns about easily detecting hardware properties, but I don't see a requirement in the spec that the list of types supported not be dependent on hardware encoding capability. Is it just Chrome's specific policy that new codecs/types are not supported in the UA unless software encoding is available for all platforms? -- GitHub Notification of comment by npdoty Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/142#issuecomment-378727499 using your GitHub account
Received on Wednesday, 4 April 2018 20:04:31 UTC