Second Screen Working Group - Activity in 2021
No matches.
Lifecycle
-
1 charter extension.
-
Charter extended until 30 June 2022.
-
Participants
-
4 participants joined.
-
KE CHEN (ByteDance) joined.
-
Alastair Coote (The New York Times) joined.
-
Mike Wasserman (Google LLC) joined.
-
Tianqi Han (Shukun (Beijing) Network Technology Co., Ltd.) joined.
-
-
3 organizations joined.
-
ByteDance joined.
-
The New York Times joined.
-
Shukun (Beijing) Network Technology Co., Ltd. joined.
-
GitHub
w3c/window-management
-
1 pull request opened.
-
Add msw as a spec editor; expand introduction. w3c/window-management#73, by @michaelwasserman.
-
-
1 pull request merged.
-
Add msw as a spec editor; expand introduction. w3c/window-management#73.
-
w3c/remote-playback
-
1 issue closed.
-
example w3c/remote-playback#144.
-
w3c/openscreenprotocol
-
1 issue received 1 new comment.
-
[Remote Playback] Capabilities for HDR rendering and display w3c/openscreenprotocol#194 (1 comment by @chrisn)
-
w3c/secondscreen-charter
-
1 issue opened.
-
OpenScreen Protocol state is no longer adopted from CG w3c/secondscreen-charter#27, by @dontcallmedom.
-
-
1 issue closed.
-
OpenScreen Protocol state is no longer adopted from CG w3c/secondscreen-charter#27.
-
-
3 issues received 5 new comments.
-
fingerprinting mitigations for multi-screen window placement w3c/secondscreen-charter#26 (3 comments by @michaelwasserman, @pes10k)
-
-
1 pull request opened.
-
Use consistent "display" terminology in scope section w3c/secondscreen-charter#28, by @tidoust.
-
-
1 pull request merged.
-
Use consistent "display" terminology in scope section w3c/secondscreen-charter#28.
-
-
1 pull request received 1 new comment.
-
Use consistent "display" terminology in scope section w3c/secondscreen-charter#28 (1 comment by @anssiko)
-
GitHub
w3c/window-management
-
4 issues closed.
-
bikeshed: window.getScreens().screens is an odd naming pattern w3c/window-management#50.
-
Spec: Define the multi-screen origin, clarify primary screen origin definition w3c/window-management#64.
-
ScreensAdvanced.isExtended mixes system-level concepts with individual screen attributes w3c/window-management#52.
-
bikeshed: consider naming the permission multiscreen instead of window-placement w3c/window-management#54.
-
-
2 issues received 4 new comments.
-
ScreensAdvanced.isExtended mixes system-level concepts with individual screen attributes w3c/window-management#52 (2 comments by @quisquous, @reillyeon)
-
bikeshed: consider naming the permission multiscreen instead of window-placement w3c/window-management#54 (2 comments by @inexorabletash, @quisquous)
-
-
4 pull requests opened.
-
spec: sort screens by x, then y w3c/window-management#72, by @quisquous.
-
Clean up various bikeshed issues, remove a lingering id reference, and update permissions integration w3c/window-management#71, by @inexorabletash.
-
Define the multi-screen origin w3c/window-management#70, by @quisquous.
-
Update explainer and spec for API renaming/removals w3c/window-management#69, by @quisquous.
-
-
4 pull requests merged.
-
spec: sort screens by x, then y w3c/window-management#72.
-
Clean up various bikeshed issues, remove a lingering id reference, and update permissions integration w3c/window-management#71.
-
Define the multi-screen origin w3c/window-management#70.
-
Update explainer and spec for API renaming/removals w3c/window-management#69.
-
-
3 pull requests received 11 new comments.
-
Update explainer and spec for API renaming/removals w3c/window-management#69 (8 comments by @inexorabletash, @quisquous, @tomayac)
-
w3c/secondscreen-charter
-
3 issues opened.
-
fingerprinting mitigations for multi-screen window placement w3c/secondscreen-charter#26, by @samuelweiler.
-
authorization missing? w3c/secondscreen-charter#25, by @samuelweiler.
-
no mandatory-to-implement codecs? w3c/secondscreen-charter#24, by @samuelweiler.
-
-
3 issues received 4 new comments.
-
fingerprinting mitigations for multi-screen window placement w3c/secondscreen-charter#26 (2 comments by @anssiko, @tidoust)
-
-
3 pull requests opened.
-
Add tidy automation w3c/secondscreen-charter#22, by @anssiko.
-
Add tidy-html5 config for the charter w3c/secondscreen-charter#21, by @markafoltz.
-
Updated draft of 2021 re-charter for the Second Screen Working Group. w3c/secondscreen-charter#20, by @markafoltz.
-
-
3 pull requests merged.
-
Updated draft of 2021 re-charter for the Second Screen Working Group. w3c/secondscreen-charter#20.
-
Add tidy automation w3c/secondscreen-charter#22.
-
Add tidy-html5 config for the charter w3c/secondscreen-charter#21.
-
-
4 pull requests received 17 new comments.
-
Updated draft of 2021 re-charter for the Second Screen Working Group. w3c/secondscreen-charter#20 (11 comments by @anssiko, @markafoltz, @tidoust)
-
w3c/secondscreen-charter#23 (1 comment by @anssiko)
-
w3c/openscreenprotocol
-
1 issue received 1 new comment.
-
[Remote Playback] Capabilities for HDR rendering and display w3c/openscreenprotocol#194 (1 comment by @chrisn)
-
-
1 pull request merged.
-
Proposed modifications to sections 9.2, 9.3, and 12.1.1 w3c/openscreenprotocol#286.
-
-
1 pull request received 1 new comment.
-
Proposed modifications to sections 9.2, 9.3, and 12.1.1 w3c/openscreenprotocol#286 (1 comment by @anssiko)
-
w3c/presentation-api
-
1 issue opened.
-
Presentation API cast app ID's broken on chromium 95 w3c/presentation-api#500, by @ThaUnknown.
-
-
1 issue closed.
-
Presentation API cast app ID's broken on chromium 95 w3c/presentation-api#500.
-
-
1 issue received 2 new comments.
-
Presentation API cast app ID's broken on chromium 95 w3c/presentation-api#500 (2 comments by @anssiko, @markafoltz)
-
Past meetings
GitHub
w3c/window-management
-
2 issues opened.
-
Support for window placement in Wayland w3c/window-management#68, by @michaelwasserman.
-
Collecting Developer Feedback w3c/window-management#67, by @michaelwasserman.
-
-
8 issues closed.
-
Should screens.currentScreen be [SameObject] ? w3c/window-management#49.
-
Can I test the API using local files? w3c/window-management#46.
-
Support for window placement on dual-screen or foldable devices? w3c/window-management#44.
-
colorDepth and pixelDepth w3c/window-management#42.
-
Integrate with Window Segmentation API w3c/window-management#35.
-
Request to track the "active" screen w3c/window-management#17.
-
Reuse existing Screen interface or add something new? w3c/window-management#18.
-
screenschange is easy to mistake for screenchange w3c/window-management#12.
-
-
25 issues received 28 new comments.
-
Spec: Define the multi-screen origin, clarify primary screen origin definition w3c/window-management#64 (1 comment by @michaelwasserman)
-
bikeshed: consider naming the permission multiscreen instead of window-placement w3c/window-management#54 (1 comment by @michaelwasserman)
-
ScreensAdvanced.isExtended mixes system-level concepts with individual screen attributes w3c/window-management#52 (1 comment by @michaelwasserman)
-
Should screens.currentScreen be [SameObject] ? w3c/window-management#49 (1 comment by @michaelwasserman)
-
Feature-parity with `app.window.create(..., { frame: 'none' })` available in Chrome Apps platform w3c/window-management#48 (1 comment by @michaelwasserman)
-
Support for window placement on dual-screen or foldable devices? w3c/window-management#44 (1 comment by @michaelwasserman)
-
Explore window-reuse nuances of cross-screen fullscreen w3c/window-management#38 (1 comment by @michaelwasserman)
-
Should `onscreenschange` provide useful data? w3c/window-management#28 (1 comment by @michaelwasserman)
-
Specify the order of returned screen objects w3c/window-management#19 (1 comment by @michaelwasserman)
-
Reuse existing Screen interface or add something new? w3c/window-management#18 (1 comment by @michaelwasserman)
-
screenschange is easy to mistake for screenchange w3c/window-management#12 (1 comment by @michaelwasserman)
-
Additional ability for window to stay on top of other windows w3c/window-management#10 (1 comment by @michaelwasserman)
-
window.open should support the 'fullscreen' option w3c/window-management#7 (1 comment by @michaelwasserman)
-
Interactions of fullscreen windows while moving between displays w3c/window-management#5 (1 comment by @michaelwasserman)
-
bikeshed: window.getScreens().screens is an odd naming pattern w3c/window-management#50 (1 comment by @michaelwasserman)
w3c/openscreenprotocol
-
2 issues closed.
-
Add a back pressure signal for media remoting w3c/openscreenprotocol#241.
-
[mDNS] OpenScreenProtocol should not restrict DNS-SD to mDNS w3c/openscreenprotocol#273.
-
-
4 issues received 10 new comments.
-
TLS SNI requirement is incompatible with TLS SNI definition w3c/openscreenprotocol#275 (4 comments by @enygren, @kaduk, @markafoltz, @sleevi)
-
[Remote Playback] Capabilities for HDR rendering and display w3c/openscreenprotocol#194 (4 comments by @anssiko, @chrisn, @louaybassbouss, @markafoltz)
-
[mDNS] OpenScreenProtocol should not restrict DNS-SD to mDNS w3c/openscreenprotocol#273 (1 comment by @markafoltz)
-
-
1 pull request opened.
-
Fixes algorithm and signing fields in agent certificate. w3c/openscreenprotocol#288, by @markafoltz.
-
-
1 pull request merged.
-
Allow additional discovery mechanisms. w3c/openscreenprotocol#283.
-
-
4 pull requests received 6 new comments.
-
Reference Media Capabilities ColorGamut for color space capability w3c/openscreenprotocol#225 (1 comment by @markafoltz)
-
Fixes algorithm and signing fields in agent certificate. w3c/openscreenprotocol#288 (1 comment by @markafoltz)
-
Proposed modifications to sections 9.2, 9.3, and 12.1.1 w3c/openscreenprotocol#286 (1 comment by @wseltzer)
w3c/presentation-api
-
1 issue closed.
-
Possibility for UA to close the connection when it is no longer operational w3c/presentation-api#485.
-
-
1 issue received 1 new comment.
-
Possibility for UA to close the connection when it is no longer operational w3c/presentation-api#485 (1 comment by @markafoltz)
-
-
2 pull requests opened.
-
Fix xref link to permission descriptor types w3c/presentation-api#499, by @tidoust.
-
Add a note about keep-alive mechanism at the app level w3c/presentation-api#498, by @tidoust.
-
-
2 pull requests merged.
-
Add a note about keep-alive mechanism at the app level w3c/presentation-api#498.
-
Fix xref link to permission descriptor types w3c/presentation-api#499.
-
-
2 pull requests received 2 new comments.
-
Add a note about keep-alive mechanism at the app level w3c/presentation-api#498 (1 comment by @markafoltz)
-
w3c/remote-playback
-
1 issue received 1 new comment.
-
Remote Playback API tests and implementation report w3c/remote-playback#92 (1 comment by @louaybassbouss)
-
w3c/secondscreen-wg
-
1 issue received 8 new comments.
-
Second Screen WG/CG - TPAC 2021 agenda w3c/secondscreen-wg#3 (8 comments by @anssiko, @chrisn, @dlibby-, @GrumpyOldTroll, @louaybassbouss, @markafoltz)
-
w3c/secondscreen-charter
-
2 pull requests opened.
-
Update boilerplate text to latest version of charter templare w3c/secondscreen-charter#19, by @tidoust.
-
Update draft charter to add latest updates to real charter w3c/secondscreen-charter#18, by @tidoust.
-
-
2 pull requests merged.
-
Update boilerplate text to latest version of charter templare w3c/secondscreen-charter#19.
-
Update draft charter to add latest updates to real charter w3c/secondscreen-charter#18.
-
Participants
-
1 participant left.
-
Soonbo Han (LG Electronics) left.
-
GitHub
w3c/openscreenprotocol
-
1 issue opened.
-
Clarify `time-scale` field w3c/openscreenprotocol#287, by @chrisn.
-
w3c/window-management
-
1 issue opened.
-
Provide Physical Dimensions / PPI of Displays w3c/window-management#65, by @seflless.
-
-
1 issue reopened.
-
Should `onscreenschange` provide useful data? w3c/window-management#28, by @michaelwasserman.
-
-
5 issues received 6 new comments.
-
Should `onscreenschange` provide useful data? w3c/window-management#28 (2 comments by @Garbee, @michaelwasserman)
-
No easy way to listen to changes to all screen attributes w3c/window-management#51 (1 comment by @michaelwasserman)
-
window.open should support the 'fullscreen' option w3c/window-management#7 (1 comment by @michaelwasserman)
-
bikeshed: window.getScreens().screens is an odd naming pattern w3c/window-management#50 (1 comment by @kenchris)
-
Provide Physical Dimensions / PPI of Displays w3c/window-management#65 (1 comment by @michaelwasserman)
-
-
1 pull request opened.
-
Fixes typo w3c/window-management#66, by @mootari.
-
-
1 pull request merged.
-
Fixes typo w3c/window-management#66.
-
GitHub
w3c/secondscreen-wg
-
1 issue opened.
-
Second Screen WG/CG - TPAC 2021 agenda w3c/secondscreen-wg#3, by @anssiko.
-
w3c/presentation-api
-
1 pull request closed.
-
Add support for allowing same-screen display w3c/presentation-api#479.
-
-
1 pull request received 1 new comment.
w3c/openscreenprotocol
-
1 pull request opened.
-
Proposed modifications to sections 9.2, 9.3, and 12.1.1 w3c/openscreenprotocol#286, by @eric-carlson.
-
-
1 pull request received 2 new comments.
-
Proposed modifications to sections 9.2, 9.3, and 12.1.1 w3c/openscreenprotocol#286 (2 comments by @anssiko, @louaybassbouss)
-
w3c/window-management
-
1 issue opened.
-
Spec: Define the multi-screen origin, clarify primary screen origin definition w3c/window-management#64, by @michaelwasserman.
-
-
2 pull requests opened.
-
Update pointers to link capturing APIs. w3c/window-management#63, by @evanstade.
-
Add quick reference to Window Placement. w3c/window-management#62, by @jpmedley.
-
-
3 pull requests merged.
-
Add quick reference to Window Placement. w3c/window-management#62.
-
Update pointers to link capturing APIs. w3c/window-management#63.
-
Update explainer and changes with permission policy w3c/window-management#59.
-
-
2 pull requests received 48 new comments.
-
Add quick reference to Window Placement. w3c/window-management#62 (47 comments by @inexorabletash, @jpmedley, @michaelwasserman)
-
Update explainer and changes with permission policy w3c/window-management#59 (1 comment by @quisquous)
-
GitHub
w3c/window-management
-
1 issue received 1 new comment.
-
bikeshed: window.getScreens().screens is an odd naming pattern w3c/window-management#50 (1 comment by @michaelwasserman)
-
-
3 pull requests opened.
-
Update index.bs syntax for a {{Window}} mention w3c/window-management#61, by @michaelwasserman.
-
Use auto-publish workflow to build spec. w3c/window-management#60, by @inexorabletash.
-
Update explainer and changes with permission policy w3c/window-management#59, by @quisquous.
-
-
2 pull requests merged.
-
Update index.bs syntax for a {{Window}} mention w3c/window-management#61.
-
Use auto-publish workflow to build spec. w3c/window-management#60.
-
-
1 pull request received 5 new comments.
-
Update explainer and changes with permission policy w3c/window-management#59 (5 comments by @inexorabletash, @michaelwasserman, @quisquous)
-
w3c/presentation-api
-
1 issue closed.
-
Same-screen presentation w3c/presentation-api#476.
-
-
1 issue received 1 new comment.
Participants
-
2 participants joined.
-
William Holroyd (Lenovo) joined.
-
Rod Waltermann (Lenovo) joined.
-
-
1 organization joined.
-
Lenovo joined.
-
GitHub
w3c/openscreenprotocol
-
1 issue received 1 new comment.
-
[Remote Playback] Capabilities for HDR rendering and display w3c/openscreenprotocol#194 (1 comment by @markafoltz)
-
-
1 pull request opened.
-
chore: rename pr-push.yml to auto-publish.yml w3c/openscreenprotocol#285, by @marcoscaceres.
-
-
1 pull request merged.
-
chore: rename pr-push.yml to auto-publish.yml w3c/openscreenprotocol#285.
-
-
1 pull request received 1 new comment.
w3c/window-management
-
1 issue received 1 new comment.
-
Should `onscreenschange` provide useful data? w3c/window-management#28 (1 comment by @michaelwasserman)
-
-
1 pull request merged.
-
Update API to match the Explainer. w3c/window-management#53.
-
-
1 pull request received 12 new comments.
-
Update API to match the Explainer. w3c/window-management#53 (12 comments by @inexorabletash, @quisquous)
-
GitHub
w3c/openscreenprotocol
-
1 issue opened.
-
Seek horizontal reviews on the spec w3c/openscreenprotocol#284, by @tidoust.
-
-
1 issue closed.
-
Rename default branch to "main" w3c/openscreenprotocol#274.
-
-
3 issues received 7 new comments.
-
[Remote Playback] Capabilities for HDR rendering and display w3c/openscreenprotocol#194 (4 comments by @anssiko, @chrisn)
-
-
1 pull request merged.
-
Update references to default branch to use "main" w3c/openscreenprotocol#281.
-
w3c/window-management
-
1 issue reopened.
-
Should screens.currentScreen be [SameObject] ? w3c/window-management#49, by @michaelwasserman.
-
-
3 issues received 4 new comments.
-
Should screens.currentScreen be [SameObject] ? w3c/window-management#49 (2 comments by @michaelwasserman, @quisquous)
-
bikeshed: window.getScreens().screens is an odd naming pattern w3c/window-management#50 (1 comment by @quisquous)
-
-
1 pull request opened.
-
Update explainer to reflect new events w3c/window-management#58, by @quisquous.
-
-
1 pull request merged.
-
Update explainer to reflect new events w3c/window-management#58.
-
-
1 pull request received 1 new comment.
w3c/remote-playback
-
1 pull request merged.
-
Fix "allowed to show a popup" concept w3c/remote-playback#142.
-
-
1 pull request received 2 new comments.
GitHub
w3c/window-management
-
3 issues opened.
-
Spec link no longer works w3c/window-management#57, by @tomayac.
-
Rename default branch to 'main' w3c/window-management#56, by @inexorabletash.
-
bikeshed: consider naming the permission multiscreen instead of window-placement w3c/window-management#54, by @quisquous.
-
-
2 issues closed.
-
Spec link no longer works w3c/window-management#57.
-
Rename default branch to 'main' w3c/window-management#56.
-
-
4 issues received 8 new comments.
-
Should screens.currentScreen be [SameObject] ? w3c/window-management#49 (2 comments by @michaelwasserman, @quisquous)
-
ScreensAdvanced.isExtended mixes system-level concepts with individual screen attributes w3c/window-management#52 (1 comment by @quisquous)
-
1 pull request opened.
-
Make currentScreen [SameObject], update onchange comment w3c/window-management#55, by @michaelwasserman.
-
-
1 pull request merged.
-
Make currentScreen [SameObject], update onchange comment w3c/window-management#55.
-
-
1 pull request received 2 new comments.
-
Update API to match the Explainer. w3c/window-management#53 (2 comments by @anssiko, @inexorabletash)
-
w3c/openscreenprotocol
-
8 issues opened.
-
Certificates should have a maximum lifetime, and SPAKE2 identities should be SPKI not cert fingerprint w3c/openscreenprotocol#282, by @estark37.
-
Clarify the supported signature algorithms for certificates w3c/openscreenprotocol#280, by @sleevi.
-
The keyUsage name is digitalSignature, not signing w3c/openscreenprotocol#279, by @sleevi.
-
Do not use Distinguished Name to convey protocol details w3c/openscreenprotocol#278, by @sleevi.
-
Consider removing support for P-521 w3c/openscreenprotocol#277, by @sleevi.
-
Agent Certificate has a circular dependency on itself w3c/openscreenprotocol#276, by @sleevi.
-
TLS SNI requirement is incompatible with TLS SNI definition w3c/openscreenprotocol#275, by @sleevi.
-
Rename default branch to "main" w3c/openscreenprotocol#274, by @tidoust.
-
-
1 issue received 2 new comments.
-
[mDNS] OpenScreenProtocol should not restrict DNS-SD to mDNS w3c/openscreenprotocol#273 (2 comments by @DavidSchinazi, @markafoltz)
-
-
2 pull requests opened.
-
Allow additional discovery mechanisms. w3c/openscreenprotocol#283, by @markafoltz.
-
Update references to default branch to use "main" w3c/openscreenprotocol#281, by @tidoust.
-
-
1 pull request received 6 new comments.
-
Allow additional discovery mechanisms. w3c/openscreenprotocol#283 (6 comments by @DavidSchinazi, @louaybassbouss, @markafoltz)
-
TR publications
-
1 document published.
-
Open Screen Protocol published as a First Public Working Draft. History of Open Screen Protocol
-
GitHub
w3c/window-management
-
5 issues opened.
-
ScreensAdvanced.isExtended mixes system-level concepts with individual screen attributes w3c/window-management#52, by @quisquous.
-
No easy way to listen to changes to all screen attributes w3c/window-management#51, by @quisquous.
-
bikeshed: window.getScreens().screens is an odd naming pattern w3c/window-management#50, by @quisquous.
-
Should screens.currentScreen be [SameObject] ? w3c/window-management#49, by @inexorabletash.
-
Feature-parity with `app.window.create(..., { frame: 'none' })` available in Chrome Apps platform w3c/window-management#48, by @exikyut.
-
-
1 issue closed.
-
Explain how this is related to the Foldables proposal w3c/window-management#21.
-
-
4 issues received 4 new comments.
-
ScreensAdvanced.isExtended mixes system-level concepts with individual screen attributes w3c/window-management#52 (1 comment by @quisquous)
-
Should screens.currentScreen be [SameObject] ? w3c/window-management#49 (1 comment by @inexorabletash)
-
Feature-parity with `app.window.create(..., { frame: 'none' })` available in Chrome Apps platform w3c/window-management#48 (1 comment by @inexorabletash)
-
Explain how this is related to the Foldables proposal w3c/window-management#21 (1 comment by @michaelwasserman)
-
-
1 pull request opened.
-
Update API to match the Explainer. w3c/window-management#53, by @inexorabletash.
-
w3c/openscreenprotocol
-
6 issues opened.
-
[mDNS] OpenScreenProtocol should not restrict DNS-SD to mDNS w3c/openscreenprotocol#273, by @DavidSchinazi.
-
Define or remove codec-specific parameters from streaming-capabilities-response. w3c/openscreenprotocol#266, by @markafoltz.
-
Should media resource URLs be optional? w3c/openscreenprotocol#265, by @markafoltz.
-
Editorial: convert HtmlMediaElements to autolinks w3c/openscreenprotocol#264, by @markafoltz.
-
travis-ci jobs to commit index.html changes are failing w3c/openscreenprotocol#259, by @markafoltz.
-
Align Streaming Protocol Capabilities with Media Capabilities? w3c/openscreenprotocol#256, by @tidoust.
-
-
8 issues closed.
-
[meta] Publish First Public Working Draft w3c/openscreenprotocol#249.
-
Editorial: convert HtmlMediaElements to autolinks w3c/openscreenprotocol#264.
-
Survey on registries w3c/openscreenprotocol#250.
-
Make a required/default remote playback state table w3c/openscreenprotocol#148.
-
Do agents need to support the Cookies extension (used in HelloRetryRequest)? w3c/openscreenprotocol#219.
-
Determine if there is an advantage to session resumption outside of early data. w3c/openscreenprotocol#220.
-
mv value needs encoding specified w3c/openscreenprotocol#239.
-
Meaning of receives-audio and receives-video capabilities. w3c/openscreenprotocol#200.
-
-
1 issue reopened.
-
travis-ci jobs to commit index.html changes are failing w3c/openscreenprotocol#259, by @markafoltz.
-
-
13 issues received 31 new comments.
-
[meta] Publish First Public Working Draft w3c/openscreenprotocol#249 (12 comments by @anssiko, @markafoltz, @tidoust)
-
travis-ci jobs to commit index.html changes are failing w3c/openscreenprotocol#259 (6 comments by @markafoltz, @tidoust)
-
[mDNS] OpenScreenProtocol should not restrict DNS-SD to mDNS w3c/openscreenprotocol#273 (2 comments by @DavidSchinazi, @louaybassbouss)
-
Editorial: convert HtmlMediaElements to autolinks w3c/openscreenprotocol#264 (2 comments by @louaybassbouss, @tidoust)
-
[Remote Playback] Capabilities for HDR rendering and display w3c/openscreenprotocol#194 (1 comment by @markafoltz)
-
Make a required/default remote playback state table w3c/openscreenprotocol#148 (1 comment by @markafoltz)
-
Do agents need to support the Cookies extension (used in HelloRetryRequest)? w3c/openscreenprotocol#219 (1 comment by @markafoltz)
-
Determine if there is an advantage to session resumption outside of early data. w3c/openscreenprotocol#220 (1 comment by @markafoltz)
-
Align Streaming Protocol Capabilities with Media Capabilities? w3c/openscreenprotocol#256 (1 comment by @markafoltz)
-
-
12 pull requests opened.
-
Advertise TR URL in the spec w3c/openscreenprotocol#272, by @anssiko.
-
Add DIAL as an example protocol to the explainer. w3c/openscreenprotocol#271, by @markafoltz.
-
Update README.md w3c/openscreenprotocol#270, by @markafoltz.
-
Convert HTMLMediaElements links to autolinks w3c/openscreenprotocol#269, by @tidoust.
-
Add link to Issue 233. w3c/openscreenprotocol#268, by @markafoltz.
-
Update issue links. w3c/openscreenprotocol#267, by @markafoltz.
-
Clarify why source is required in remote-playback-start-response. w3c/openscreenprotocol#263, by @markafoltz.
-
Switch build to GitHub action using spec-prod w3c/openscreenprotocol#262, by @tidoust.
-
Revert "travis-ci: refer to variables directly." w3c/openscreenprotocol#261, by @markafoltz.
-
travis-ci: refer to variables directly. w3c/openscreenprotocol#260, by @markafoltz.
-
Re-land "Update TLS usage." w3c/openscreenprotocol#258, by @markafoltz.
-
Revert "Update TLS usage." w3c/openscreenprotocol#257, by @markafoltz.
-
-
17 pull requests merged.
-
Advertise TR URL in the spec w3c/openscreenprotocol#272.
-
Adds a backpressure signal to the streaming protocol. w3c/openscreenprotocol#248.
-
Add DIAL as an example protocol to the explainer. w3c/openscreenprotocol#271.
-
Convert HTMLMediaElements links to autolinks w3c/openscreenprotocol#269.
-
Draft of Open Screen Protocol explainer document w3c/openscreenprotocol#168.
-
Update README.md w3c/openscreenprotocol#270.
-
Add link to Issue 233. w3c/openscreenprotocol#268.
-
Switch build to GitHub action using spec-prod w3c/openscreenprotocol#262.
-
Update issue links. w3c/openscreenprotocol#267.
-
Clarify why source is required in remote-playback-start-response. w3c/openscreenprotocol#263.
-
Update definitions of receives-audio and receives-video. w3c/openscreenprotocol#255.
-
Specify coding of mv. w3c/openscreenprotocol#253.
-
Revert "travis-ci: refer to variables directly." w3c/openscreenprotocol#261.
-
travis-ci: refer to variables directly. w3c/openscreenprotocol#260.
-
Re-land "Update TLS usage." w3c/openscreenprotocol#258.
-
Revert "Update TLS usage." w3c/openscreenprotocol#257.
-
Update TLS usage. w3c/openscreenprotocol#252.
-
-
11 pull requests received 37 new comments.
-
Draft of Open Screen Protocol explainer document w3c/openscreenprotocol#168 (10 comments by @louaybassbouss, @markafoltz)
-
Switch build to GitHub action using spec-prod w3c/openscreenprotocol#262 (9 comments by @markafoltz, @tidoust)
-
Adds a backpressure signal to the streaming protocol. w3c/openscreenprotocol#248 (8 comments by @anssiko, @chrisn, @louaybassbouss, @markafoltz)
-
Add DIAL as an example protocol to the explainer. w3c/openscreenprotocol#271 (1 comment by @louaybassbouss)
-
Convert HTMLMediaElements links to autolinks w3c/openscreenprotocol#269 (1 comment by @louaybassbouss)
-
Update definitions of receives-audio and receives-video. w3c/openscreenprotocol#255 (1 comment by @markafoltz)
-
Reference Media Capabilities ColorGamut for color space capability w3c/openscreenprotocol#225 (1 comment by @tidoust)
-
w3c/presentation-api
-
1 issue closed.
-
Requesting enhancements to the presentation API w3c/presentation-api#477.
-
-
1 issue received 1 new comment.
Participants
-
3 participants joined.
-
Pavlo Buidenkov (W3C Invited Experts) joined.
-
Diego Gonzalez-Zuniga (Microsoft Corporation) joined.
-
Geunhyung Kim (Gooroomee Inc.) joined.
-
-
1 organization joined.
-
Gooroomee Inc. joined.
-
GitHub
w3c/presentation-api
-
1 issue closed.
-
Presentation-api cast file working good on Chrome version 87, but it is not work on Chrome version 88 w3c/presentation-api#497.
-
-
2 issues received 9 new comments.
-
Presentation-api cast file working good on Chrome version 87, but it is not work on Chrome version 88 w3c/presentation-api#497 (7 comments by @binhhuynhgit, @eliasmikkola, @markafoltz, @rdrrichards)
-
Requesting enhancements to the presentation API w3c/presentation-api#477 (2 comments by @anssiko, @rdrrichards)
-
w3c/openscreenprotocol
-
1 issue opened.
-
[Capabilities] Finish the capabilities table. w3c/openscreenprotocol#254, by @markafoltz.
-
-
3 issues received 7 new comments.
-
[meta] Publish First Public Working Draft w3c/openscreenprotocol#249 (3 comments by @anssiko, @markafoltz)
-
[Remote Playback] Capabilities for HDR rendering and display w3c/openscreenprotocol#194 (1 comment by @anssiko)
-
-
4 pull requests opened.
-
Update definitions of receives-audio and receives-video. w3c/openscreenprotocol#255, by @markafoltz.
-
Specify coding of mv. w3c/openscreenprotocol#253, by @markafoltz.
-
Update TLS usage. w3c/openscreenprotocol#252, by @markafoltz.
-
Update reference to CBOR RFC. w3c/openscreenprotocol#251, by @markafoltz.
-
-
1 pull request merged.
-
Update reference to CBOR RFC. w3c/openscreenprotocol#251.
-
-
5 pull requests received 9 new comments.
-
Reference Media Capabilities ColorGamut for color space capability w3c/openscreenprotocol#225 (3 comments by @markafoltz)
-
Adds a backpressure signal to the streaming protocol. w3c/openscreenprotocol#248 (1 comment by @markafoltz)
w3c/window-management
-
3 issues closed.
-
Why `scaleFactor` and not `devicePixelRatio`? w3c/window-management#29.
-
Should `touchSupport` be `pointerTypes`? w3c/window-management#31.
-
Reference complementary proposals w3c/window-management#40.
-
-
3 issues received 3 new comments.
-
Why `scaleFactor` and not `devicePixelRatio`? w3c/window-management#29 (1 comment by @michaelwasserman)
-
w3c/secondscreen-wg
-
1 issue received 7 new comments.
-
Second Screen WG/CG - 2021 Q1 virtual meeting w3c/secondscreen-wg#2 (7 comments by @anssiko, @dlibby-, @kenchris, @louaybassbouss, @markafoltz)
-
w3c/remote-playback
-
1 issue opened.
-
render a dummy video/progress bar w3c/remote-playback#143, by @jimmywarting.
-
Participants
-
1 chair appointed.
-
Louay Bassbouss became a chair.
-
-
7 participants left.
-
Rang-Hyuck Lee (Gooroomee Inc.) left.
-
Joshue O'Connor (W3C) left.
-
Kasar Masood (SPORTTOTAL AG) left.
-
Geunhyung Kim (Gooroomee Inc.) left.
-
Mark Watson (Netflix Inc.) left.
-
Zouhir Chahoud (Microsoft Corporation) left.
-
Steve Morris (Espial Group Inc.) left.
-
-
3 organizations joined.
-
LG Electronics joined.
-
Google LLC joined.
-
Intel Corporation joined.
-
-
1 organization left.
-
Espial Group Inc. left.
-
GitHub
w3c/presentation-api
-
1 issue opened.
-
Presentation-api cast file working good on Chrome version 87, but it is not work on Chrome version 88 w3c/presentation-api#497, by @binhhuynhgit.
-
-
2 issues received 7 new comments.
-
Presentation-api cast file working good on Chrome version 87, but it is not work on Chrome version 88 w3c/presentation-api#497 (6 comments by @binhhuynhgit, @markafoltz, @rdrrichards)
-
Possibility for UA to close the connection when it is no longer operational w3c/presentation-api#485 (1 comment by @tidoust)
-
w3c/secondscreen-wg
-
1 issue opened.
-
Second Screen WG/CG - 2021 Q1 virtual meeting w3c/secondscreen-wg#2, by @anssiko.
-
-
1 issue received 11 new comments.
-
Second Screen WG/CG - 2021 Q1 virtual meeting w3c/secondscreen-wg#2 (11 comments by @anssiko, @chrisn, @darktears, @louaybassbouss, @markafoltz, @michaelwasserman)
-
w3c/window-management
-
1 issue opened.
-
Exposing the refresh rate of displays w3c/window-management#47, by @jespertheend.
-
-
1 issue closed.
-
Putting the event target behind a permission w3c/window-management#30.
-
-
1 issue received 1 new comment.
-
Putting the event target behind a permission w3c/window-management#30 (1 comment by @michaelwasserman)
-
w3c/openscreenprotocol
-
1 issue opened.
-
Survey on registries w3c/openscreenprotocol#250, by @tidoust.
-
-
1 issue received 1 new comment.