- From: Marcos Cáceres <notifications@github.com>
- Date: Thu, 13 Oct 2016 23:27:22 -0700
- To: w3c/manifest <manifest@noreply.github.com>
Received on Friday, 14 October 2016 06:28:04 UTC
marcoscaceres commented on this pull request. > + </li> + <li>Let <var>p</var> be a new promise. + </li> + <li>Run the following steps in parallel: + </li> + <li>Return <var>p</var>. + </li> + </ol> + </section> + <section> + <h4> + <code>userChoice</code> attribute + </h4> + <p> + The <dfn><code>userChoice</code> attribute</dfn>, when getting, + returns a promise. Agree. This is painful. My proposal would be that BIP has one internal "prompt" promise. That makes the whole design much more sensical. That promise resolves after prompt() succeeds and returns some kind of `UserPromptResult` object as proposed above. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/pull/506
Received on Friday, 14 October 2016 06:28:04 UTC