- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 02 Nov 2021 17:00:25 +0000
- To: public-secondscreen@w3.org
- Message-Id: <E1mhx97-0007Or-A1@uranus.w3.org>
Issues
------
* w3c/presentation-api (+0/-1/💬1)
1 issues received 1 new comments:
- #485 Possibility for UA to close the connection when it is no longer operational (1 by mfoltzgoogle)
https://github.com/w3c/presentation-api/issues/485
1 issues closed:
- Possibility for UA to close the connection when it is no longer operational https://github.com/w3c/presentation-api/issues/485
* w3c/openscreenprotocol (+0/-2/💬9)
4 issues received 9 new comments:
- #275 TLS SNI requirement is incompatible with TLS SNI definition (4 by enygren, kaduk, mfoltzgoogle, sleevi)
https://github.com/w3c/openscreenprotocol/issues/275 [security-tracker]
- #273 [mDNS] OpenScreenProtocol should not restrict DNS-SD to mDNS (1 by mfoltzgoogle)
https://github.com/w3c/openscreenprotocol/issues/273 [security-tracker]
- #241 Add a back pressure signal for media remoting (1 by mfoltzgoogle)
https://github.com/w3c/openscreenprotocol/issues/241 [F2F] [v1-spec]
- #194 [Remote Playback] Capabilities for HDR rendering and display (3 by anssiko, louaybassbouss, mfoltzgoogle)
https://github.com/w3c/openscreenprotocol/issues/194 [Protocol] [F2F] [v1-spec]
2 issues closed:
- Add a back pressure signal for media remoting https://github.com/w3c/openscreenprotocol/issues/241 [F2F] [v1-spec]
- [mDNS] OpenScreenProtocol should not restrict DNS-SD to mDNS https://github.com/w3c/openscreenprotocol/issues/273 [security-tracker]
* webscreens/window-placement (+1/-9/💬27)
1 issues created:
- Support for window placement in Wayland (by michaelwasserman)
https://github.com/webscreens/window-placement/issues/68 [question]
24 issues received 27 new comments:
- #64 Spec: Define the multi-screen origin, clarify primary screen origin definition (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/64 [documentation]
- #54 bikeshed: consider naming the permission multiscreen instead of window-placement (3 by inexorabletash, michaelwasserman, quisquous)
https://github.com/webscreens/window-placement/issues/54 [question]
- #52 ScreensAdvanced.isExtended mixes system-level concepts with individual screen attributes (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/52 [question]
- #50 bikeshed: window.getScreens().screens is an odd naming pattern (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/50
- #49 Should screens.currentScreen be [SameObject] ? (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/49 [question]
- #48 Feature-parity with `app.window.create(..., { frame: 'none' })` available in Chrome Apps platform (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/48 [enhancement]
- #47 Exposing the refresh rate of displays (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/47 [enhancement]
- #46 Can I test the API using local files? (2 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/46
- #44 Support for window placement on dual-screen or foldable devices? (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/44 [enhancement] [question]
- #42 colorDepth and pixelDepth (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/42 [question] [wontfix]
- #41 Align terminology across related specs (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/41 [documentation]
- #38 Explore window-reuse nuances of cross-screen fullscreen (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/38 [enhancement] [question]
- #35 Integrate with Window Segmentation API (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/35 [documentation] [enhancement] [question]
- #28 Should `onscreenschange` provide useful data? (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/28 [enhancement] [question]
- #20 HDR / WCG (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/20 [enhancement]
- #19 Specify the order of returned screen objects (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/19 [bug] [documentation]
- #18 Reuse existing Screen interface or add something new? (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/18 [question]
- #17 Request to track the "active" screen (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/17 [enhancement]
- #12 screenschange is easy to mistake for screenchange (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/12 [wontfix]
- #10 Additional ability for window to stay on top of other windows (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/10 [enhancement]
- #9 Feature detection support? (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/9 [documentation] [question]
- #8 Consider new APIs for window bounds (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/8 [enhancement]
- #7 window.open should support the 'fullscreen' option (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/7 [enhancement]
- #5 Interactions of fullscreen windows while moving between displays (1 by michaelwasserman)
https://github.com/webscreens/window-placement/issues/5 [documentation]
9 issues closed:
- bikeshed: consider naming the permission multiscreen instead of window-placement https://github.com/webscreens/window-placement/issues/54 [question]
- Should screens.currentScreen be [SameObject] ? https://github.com/webscreens/window-placement/issues/49 [question]
- Can I test the API using local files? https://github.com/webscreens/window-placement/issues/46
- Support for window placement on dual-screen or foldable devices? https://github.com/webscreens/window-placement/issues/44 [enhancement] [question]
- colorDepth and pixelDepth https://github.com/webscreens/window-placement/issues/42 [question] [wontfix]
- Integrate with Window Segmentation API https://github.com/webscreens/window-placement/issues/35 [documentation] [enhancement] [question]
- Request to track the "active" screen https://github.com/webscreens/window-placement/issues/17 [enhancement]
- Reuse existing Screen interface or add something new? https://github.com/webscreens/window-placement/issues/18 [question]
- screenschange is easy to mistake for screenchange https://github.com/webscreens/window-placement/issues/12 [wontfix]
Pull requests
-------------
* w3c/presentation-api (+0/-1/💬0)
1 pull requests merged:
- Add a note about keep-alive mechanism at the app level
https://github.com/w3c/presentation-api/pull/498
* w3c/openscreenprotocol (+1/-1/💬2)
1 pull requests submitted:
- Fixes algorithm and signing fields in agent certificate. (by mfoltzgoogle)
https://github.com/w3c/openscreenprotocol/pull/288
2 pull requests received 2 new comments:
- #288 Fixes algorithm and signing fields in agent certificate. (1 by mfoltzgoogle)
https://github.com/w3c/openscreenprotocol/pull/288
- #283 Allow additional discovery mechanisms. (1 by mfoltzgoogle)
https://github.com/w3c/openscreenprotocol/pull/283
1 pull requests merged:
- Allow additional discovery mechanisms.
https://github.com/w3c/openscreenprotocol/pull/283
* webscreens/window-segments (+0/-1/💬0)
1 pull requests merged:
- Add deprecation message
https://github.com/webscreens/window-segments/pull/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
* https://github.com/webscreens/form-factors
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 2 November 2021 17:00:28 UTC