- From: Daniel Burnett via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 May 2015 12:28:24 +0000
- To: public-media-capture-logs@w3.org
Okay, then there are two approaches that I think we could take: the right way, and the simple/quick way. The right way is to create two new errors: MediaStreamError (which would cover both PermissionDeniedError and SourceUnavailableError, the two that are truly errors that are specific to acquiring access to a MediaStream) and ConstraintError (which would cover both ConstraintNotSatisfiedError and OverconstrainedError, the two that are really about constraint satisfaction rather than anything to do specifically with MediaStreams). The simple way is to just call all of them a MediaStreamError since no one else is currently using constraints and figure that the constraint error pieces can be pulled out later if/when anyone else starts using constraints. One potentially complicating issue is that some of these may occur as events and not just Promise rejections. For example, OverconstrainedError (as an event) can definitely happen multiple times, and be fixed, without causing a Promise rejection. I have not vetted this on the list yet -- I'm just trying to get a rough sense from you of what might be reasonable and to make sure that I didn't miss any major specification pieces. -- GitHub Notif of comment by burnburn See https://github.com/w3c/mediacapture-main/pull/170#issuecomment-104254547
Received on Thursday, 21 May 2015 12:28:25 UTC