- From: via GitHub <sysbot+gh@w3.org>
- Date: Fri, 29 May 2015 16:59:56 +0000
- To: public-media-capture-logs@w3.org
@jan-ivar, here is an example to clarify what I mean by observable:
getUserMedia({}).catch(function() { console.log("gum rejected") })
new Promise(function(resolve, reject) { reject() }).catch(function() {
console.log("promise rejected") })
The second promise callback will be called before or after the first
promise callback depending on how is implemented step 3.2.
Is the spec prescribing a specific order for the example above?
I tend to think so but maybe I am too restrictive in my interpretation
of the spec.
More generally, cases like user prompting or system calls seem
different to straightforward value/state checking. Some other
promise-based APIs (streams API, AudioContext...) may be useful to
check.
@adam-be, yes, moving 3.1 and 3.2 out of the async seems like an
improvement to me.
But I am not pushing hard for that yet. I am more looking at
clarifying the intent of the spec.
--
GitHub Notif of comment by youennf
See
https://github.com/w3c/mediacapture-main/issues/174#issuecomment-106871015
Received on Friday, 29 May 2015 16:59:57 UTC