- From: via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 May 2015 18:48:20 +0000
- To: public-media-capture-logs@w3.org
As I read it, the spec rules out implementation that could reject/resolve the promise synchronously. That is unfortunate. In WebKit, step 3.2 is about to be implemented synchronously. >From the JS end-user prospective, this does not matter, the promise will call the reject callback asynchronously anyway. If we were to follow closely the spec (or my interpretation of it), we would: 1. schedule an asynchronous call in which we would: 1.a check that the dictionary is empty. 1.b. reject the promise. 2. schedule another asynchronous call to actually call the promise reject callback. This seems like unnecessary overhead. The same may be applied to step 3.5. If the browser knows already that the getUserMedia call will fail, why schedule an asynchronous call to reject the promise? The spec should allow that behavior. -- GitHub Notif of comment by youennf See https://github.com/w3c/mediacapture-main/issues/174#issuecomment-106564066
Received on Thursday, 28 May 2015 18:48:22 UTC