- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Mon, 15 Sep 2014 14:34:03 +0000
- To: "public-webscreens@w3.org" <public-webscreens@w3.org>, "mark a. foltz" <mfoltz@google.com>
- CC: Anton Vayvod <avayvod@google.com>, Yuri Wiitala <miu@google.com>, "Derek Cheng" <imcheng@google.com>
Hi MarkFo, Yuri, Anton, All, >From [1]: On 10 Sep 2014, at 21:01, mark a. foltz <mfoltz@google.com> wrote: > My colleagues Yuri and Anton have begun prototyping parts of the Presentation API in Chromium and raised the following issues which I don't believe are covered in the current specification. Listed here and filed in GH. > > (1) Are multiple simultaneous calls permitted to startSession()? My intuition is "no", but I would like to ask the group if there are any use cases where this is necessary. If the answer is "yes" it adds some constraints and complexity to the user interface for screen selection in the browser. > https://github.com/webscreens/presentation-api/issues/21 You mean that until the promise returned by startSession() has resolved, any subsequent calls to startSession() would do nothing, that is the other promise returned by subsequent calls would not resolved either? Please feel free to provide an example to illustrate what you mean if I did not get this right. All - to provide more context for this, see MarkFo’s recent PR [2] summarized at [3]. The HTML version with the PR is at [4]. MarkFo - there are still some traces of requestSession() in the sections 5 and 5.4 in your PR [2]. Thanks, -Anssi [1] https://github.com/webscreens/presentation-api/issues/21 [2] https://github.com/webscreens/presentation-api/pull/23 [3] http://lists.w3.org/Archives/Public/public-webscreens/2014Sep/0031.html [4] http://mfoltzgoogle.github.io/presentation-api/
Received on Monday, 15 September 2014 14:35:23 UTC