Re: [presentation-api] [meta] Publish Candidate Recommendation

Here's the summary of the PROPOSED RESOLUTIONs for the remaining CR 
blockers we discussed at the F2F.

@mfoltzgoogle I assume you'll update the spec to address the first 
four issues, and will sync with relevant implementers re #311 
feasibility.

@tidoust When should we have a publication ready spec for the CR 
transition request if we'd like to publish by the end of June, or soon
 after? I'd like to get the CR out before we enter the seasonally 
slower summer months.

- #99 Define behavior of Window and Fullscreen APIs in the 
presentation browsing context
  - F2F minutes: 
https://www.w3.org/2016/05/24-webscreens-minutes.html#item16
  - [ ] **PROPOSED RESOLUTION**: No change to the Presentation API, 
feature would be addressed by the CSS WG if a strong use case 
motivates it. Open another issue about recommending to add "TV" to the
 User-Agent string.
- #153 Assess interoperability of Presentation API implementations
  - F2F minutes: 
https://www.w3.org/2016/05/24-webscreens-minutes.html#item15
  - [x] **ACTION**:
     - advance with the CG chartering 
https://github.com/webscreens/cg-charter/ to incubate protocol-level 
interop
     - spun off an issue #311 impacting API interop
- #255 Is a new Permission type required for presentation display 
availability?
  - F2F minutes: 
https://www.w3.org/2016/05/24-webscreens-minutes.html#item13
  - [ ] **PROPOSED RESOLUTION**: no new permission type required
- #275 User Data Controls in Web Browsers guidelines
  - F2F minutes: 
https://www.w3.org/2016/05/24-webscreens-minutes.html#item14
  - [ ] **PROPOSED RESOLUTION**: complete the clear site data steps in
 the spec (add AppCache, Service Workers) and add non-normative note 
referencing TAG document for more complete list, add note clarifying 
this is not about defining private mode
- #311 Add presentation request URL fallback mechanism
  - F2F minutes: 
https://www.w3.org/2016/05/25-webscreens-minutes.html#item03
  - [ ] **PROPOSED RESOLUTION**: Add a fallback mechanism by adding a 
new constructor on PresentationRequest that takes an Array of 
DOMString, and by exposing the presented URL in an "url" attribute on 
PresentationConnection, pending feedback from implementers that this 
is doable.

-- 
GitHub Notification of comment by anssiko
Please view or discuss this issue at 
https://github.com/w3c/presentation-api/issues/276#issuecomment-222682736
 using your GitHub account

Received on Tuesday, 31 May 2016 13:08:40 UTC