Weekly github digest (Second Screen WG/CG repos)

Issues
------
* webscreens/screen-enumeration (+0/-16/💬17)
  17 issues received 17 new comments:
  - #34 Combine Screen Enumeration and Window Placement proposals? (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/34 
  - #33 Describe support for permission API status queries (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/33 
  - #31 Reuse existing Screen interface or add something new? (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/31 
  - #30 API design for a single multi-screen boolean (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/30 
  - #29 Reject the getScreens() Promise with permission denial (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/29 
  - #24 Async vs sync (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/24 
  - #23 Picker-style API (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/23 
  - #22 Security and privacy writeup does not discuss fingerprinting (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/22 
  - #21 What is the primary screen? (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/21 
  - #20 How are extended desktop arrangements represented? (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/20 
  - #19 Expose mirrored desktops? (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/19 
  - #17 Proposed screen properties may already be exposed via the Web (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/17 
  - #16 Use cases for screen enumeration in service workers? (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/16 
  - #14 touch support can already be feature detected (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/14 
  - #12 Should the API return static or live objects? (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/12 [question] 
  - #11 Dynamic properties (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/11 [question] 
  - #8 Should the lifetime of a Screen object be limited? (1 by michaelwasserman)
    https://github.com/webscreens/screen-enumeration/issues/8 [question] 

  16 issues closed:
  - Picker-style API https://github.com/webscreens/screen-enumeration/issues/23 
  - Should the lifetime of a Screen object be limited? https://github.com/webscreens/screen-enumeration/issues/8 [question] 
  - Should the API return static or live objects? https://github.com/webscreens/screen-enumeration/issues/12 [question] 
  - Describe support for permission API status queries https://github.com/webscreens/screen-enumeration/issues/33 
  - Async vs sync https://github.com/webscreens/screen-enumeration/issues/24 
  - Proposed screen properties may already be exposed via the Web https://github.com/webscreens/screen-enumeration/issues/17 
  - Security and privacy writeup does not discuss fingerprinting https://github.com/webscreens/screen-enumeration/issues/22 
  - What is the primary screen? https://github.com/webscreens/screen-enumeration/issues/21 
  - How are extended desktop arrangements represented? https://github.com/webscreens/screen-enumeration/issues/20 
  - Expose mirrored desktops? https://github.com/webscreens/screen-enumeration/issues/19 
  - Interaction with virtual desktops? https://github.com/webscreens/screen-enumeration/issues/18 
  - Use cases for screen enumeration in service workers? https://github.com/webscreens/screen-enumeration/issues/16 
  - touch support can already be feature detected https://github.com/webscreens/screen-enumeration/issues/14 
  - API design for a single multi-screen boolean https://github.com/webscreens/screen-enumeration/issues/30 
  - Dynamic properties https://github.com/webscreens/screen-enumeration/issues/11 [question] 
  - Combine Screen Enumeration and Window Placement proposals? https://github.com/webscreens/screen-enumeration/issues/34 

* webscreens/window-placement (+4/-1/💬3)
  4 issues created:
  - HDR / WCG (by jimbankoski)
    https://github.com/webscreens/window-placement/issues/20 
  - Specify the order of returned screen objects (by michaelwasserman)
    https://github.com/webscreens/window-placement/issues/19 
  - Reuse existing Screen interface or add something new? (by michaelwasserman)
    https://github.com/webscreens/window-placement/issues/18 
  - Request to track the "active" screen (by michaelwasserman)
    https://github.com/webscreens/window-placement/issues/17 [enhancement] 

  3 issues received 3 new comments:
  - #18 Reuse existing Screen interface or add something new? (1 by michaelwasserman)
    https://github.com/webscreens/window-placement/issues/18 
  - #17 Request to track the "active" screen (1 by michaelwasserman)
    https://github.com/webscreens/window-placement/issues/17 [enhancement] 
  - #15 Scope of the initial proposal (1 by michaelwasserman)
    https://github.com/webscreens/window-placement/issues/15 

  1 issues closed:
  - Scope of the initial proposal https://github.com/webscreens/window-placement/issues/15 




Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/presentation-api
* https://github.com/w3c/remote-playback
* https://github.com/w3c/openscreenprotocol
* https://github.com/webscreens/screen-enumeration
* https://github.com/webscreens/window-placement
* https://github.com/webscreens/window-segments


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config