- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Aug 2018 19:16:01 +0000
- To: public-media-capture-logs@w3.org
henbos has just created a new issue for https://github.com/w3c/mediacapture-screen-share: == Be consistent with how to handle errors == 5.2 says to throw an InvalidAccessError if MediaTrackConstraints are used, 5.4 says deviceId can make it overconstrained which I think implies an OverconstrainedError is thrown, and I think other parts of the spec may have implied that unsupported constraints are simply ignored (no exception thrown), but I'm not sure about that last part. - We should be consistent with how we handle errors. Should we use different exception types? - If an unsupported constraint or a constraint that doesn't make sense, should we always throw an exception? If we throw on deviceId being set we might want to throw on other recognized attributes that aren't supported being set. Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/68 using your GitHub account
Received on Friday, 24 August 2018 19:16:03 UTC