Second Screen Working Group - Activity in 2020
No matches.
Lifecycle
-
1 charter started.
-
Chartered until 31 December 2021. Participants had to rejoin under this charter.
-
Participants
-
5 organizations joined.
-
Fraunhofer Gesellschaft joined.
-
Espial Group Inc. joined.
-
Microsoft Corporation joined.
-
Apple Inc. joined.
-
British Broadcasting Corporation joined.
-
-
11 organizations left.
-
Gooroomee Inc. left.
-
Microsoft Corporation left.
-
Netflix Inc. left.
-
SPORTTOTAL AG left.
-
LG Electronics left.
-
Google LLC left.
-
Espial Group Inc. left.
-
British Broadcasting Corporation left.
-
Fraunhofer Gesellschaft left.
-
Intel Corporation left.
-
Apple Inc. left.
-
GitHub
w3c/remote-playback
-
1 pull request opened.
-
Fix "allowed to show a popup" concept w3c/remote-playback#142, by @tidoust.
-
w3c/window-management
-
1 issue opened.
-
Can I test the API using local files? w3c/window-management#46, by @jjeff.
-
-
1 issue received 4 new comments.
w3c/presentation-api
-
2 pull requests opened.
-
Adjust terminology for events w3c/presentation-api#496, by @tidoust.
-
Fix refs to "a priori authenticated URL" and "application cache" w3c/presentation-api#495, by @tidoust.
-
-
2 pull requests merged.
-
Adjust terminology for events w3c/presentation-api#496.
-
Fix refs to "a priori authenticated URL" and "application cache" w3c/presentation-api#495.
-
-
2 pull requests received 3 new comments.
-
Fix refs to "a priori authenticated URL" and "application cache" w3c/presentation-api#495 (1 comment by @markafoltz)
TR publications
-
1 document published.
-
Presentation API published as a Candidate Recommendation Draft. History of Presentation API
-
GitHub
w3c/window-management
-
1 issue opened.
-
Support for window placement on dual-screen or foldable devices? w3c/window-management#44, by @michaelwasserman.
-
-
3 issues received 5 new comments.
-
Putting the event target behind a permission w3c/window-management#30 (2 comments by @michaelwasserman, @rainke)
-
-
2 pull requests opened.
-
Update old ScreenInfo references w3c/window-management#45, by @michaelwasserman.
-
Link related explainers w3c/window-management#43, by @zouhir.
-
-
2 pull requests merged.
-
Update old ScreenInfo references w3c/window-management#45.
-
Link related explainers w3c/window-management#43.
-
-
1 pull request received 6 new comments.
-
Link related explainers w3c/window-management#43 (6 comments by @anssiko, @michaelwasserman, @zouhir)
-
w3c/openscreenprotocol
-
1 issue closed.
-
TPAC October 2020 topics w3c/openscreenprotocol#244.
-
-
1 issue received 1 new comment.
w3c/remote-playback
-
1 issue closed.
-
RemotePlaybackState enum can become misleading when changing media.src w3c/remote-playback#125.
-
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Allow remote playback device to choose the remote playback source. w3c/remote-playback#141.
-
-
1 pull request received 2 new comments.
-
Allow remote playback device to choose the remote playback source. w3c/remote-playback#141 (2 comments by @anssiko, @markafoltz)
-
w3c/presentation-api
-
1 issue closed.
-
Publish a Candidate Recommendation Draft w3c/presentation-api#488.
-
-
1 issue received 4 new comments.
-
Publish a Candidate Recommendation Draft w3c/presentation-api#488 (4 comments by @anssiko, @tidoust)
-
-
4 pull requests opened.
-
Update metadata for automated publication with Echidna w3c/presentation-api#494, by @tidoust.
-
Switch to neutral "they" for user w3c/presentation-api#493, by @tidoust.
-
Update 301 links and test suite URL w3c/presentation-api#492, by @tidoust.
-
Update SOTD to mention main normative changes since last CR w3c/presentation-api#491, by @tidoust.
-
-
4 pull requests merged.
-
Update metadata for automated publication with Echidna w3c/presentation-api#494.
-
Update SOTD to mention main normative changes since last CR w3c/presentation-api#491.
-
Switch to neutral "they" for user w3c/presentation-api#493.
-
Update 301 links and test suite URL w3c/presentation-api#492.
-
-
3 pull requests received 5 new comments.
-
Update SOTD to mention main normative changes since last CR w3c/presentation-api#491 (3 comments by @markafoltz, @tidoust)
-
Update metadata for automated publication with Echidna w3c/presentation-api#494 (1 comment by @tidoust)
-
Participants
-
2 participants joined.
-
Rang-Hyuck Lee (Gooroomee Inc.) joined.
-
Geunhyung Kim (Gooroomee Inc.) joined.
-
-
1 organization joined.
-
Gooroomee Inc. joined.
-
GitHub
w3c/presentation-api
-
2 issues opened.
-
Publish a Candidate Recommendation Draft w3c/presentation-api#488, by @anssiko.
-
Possibility for UA to close the connection when it is no longer operational w3c/presentation-api#485, by @tidoust.
-
-
4 issues closed.
-
Can the same browsing context act as a controller and receiver? w3c/presentation-api#338.
-
reconnect after termination w3c/presentation-api#480.
-
PresentationRequest is not defined? w3c/presentation-api#475.
-
send request stuck on presentationRequest.getAvailability() Method w3c/presentation-api#474.
-
-
9 issues received 16 new comments.
-
Requesting enhancements to the presentation API w3c/presentation-api#477 (4 comments by @markafoltz, @michaelwasserman, @rdrrichards)
-
Publish a Candidate Recommendation Draft w3c/presentation-api#488 (2 comments by @markafoltz, @tidoust)
-
Can the same browsing context act as a controller and receiver? w3c/presentation-api#338 (2 comments by @markafoltz)
-
Possibility for UA to close the connection when it is no longer operational w3c/presentation-api#485 (1 comment by @markafoltz)
-
Presentation reconnection with an implementation specific mechanism? w3c/presentation-api#471 (1 comment by @markafoltz)
-
send request stuck on presentationRequest.getAvailability() Method w3c/presentation-api#474 (1 comment by @markafoltz)
-
-
5 pull requests opened.
-
Re-runs tidy-html5 on the current spec. w3c/presentation-api#490, by @markafoltz.
-
Updates changelog to prepare for CRD publication. w3c/presentation-api#489, by @markafoltz.
-
Add note about controlling browsing contexts. w3c/presentation-api#487, by @markafoltz.
-
Switch to automatic cross-references w3c/presentation-api#486, by @tidoust.
-
Add note on how presentations without connections should be handled. w3c/presentation-api#484, by @markafoltz.
-
-
6 pull requests merged.
-
Updates changelog to prepare for CRD publication. w3c/presentation-api#489.
-
Re-runs tidy-html5 on the current spec. w3c/presentation-api#490.
-
Switch to automatic cross-references w3c/presentation-api#486.
-
Add note about controlling browsing contexts. w3c/presentation-api#487.
-
Editorial: Align with Web IDL specification w3c/presentation-api#482.
-
Editorial: fix link to Navigator and update Respec URL w3c/presentation-api#483.
-
-
1 pull request closed.
-
Add note on how presentations without connections should be handled. w3c/presentation-api#484.
-
-
7 pull requests received 18 new comments.
-
Add note about controlling browsing contexts. w3c/presentation-api#487 (5 comments by @louaybassbouss, @markafoltz, @tidoust)
-
Add note on how presentations without connections should be handled. w3c/presentation-api#484 (3 comments by @markafoltz, @tidoust)
-
Updates changelog to prepare for CRD publication. w3c/presentation-api#489 (2 comments by @anssiko, @markafoltz)
-
Add support for allowing same-screen display w3c/presentation-api#479 (2 comments by @dlibby-, @markafoltz)
-
Editorial: fix link to Navigator and update Respec URL w3c/presentation-api#483 (1 comment by @markafoltz)
-
w3c/window-management
-
4 issues opened.
-
colorDepth and pixelDepth w3c/window-management#42, by @fantasai.
-
Align terminology across related specs w3c/window-management#41, by @anssiko.
-
Reference complementary proposals w3c/window-management#40, by @anssiko.
-
Explore window-reuse nuances of cross-screen fullscreen w3c/window-management#38, by @michaelwasserman.
-
-
1 issue closed.
-
Find out how to integrate with Visual Viewport w3c/window-management#36.
-
-
3 issues received 5 new comments.
-
Find out how to integrate with Visual Viewport w3c/window-management#36 (3 comments by @bokand, @michaelwasserman)
-
window.open should support the 'fullscreen' option w3c/window-management#7 (1 comment by @michaelwasserman)
-
-
2 pull requests opened.
-
Add CHANGES.md describing changes after the first Origin Trial w3c/window-management#39, by @michaelwasserman.
-
Update the Explainer's proposed API shape to address recent feedback w3c/window-management#37, by @michaelwasserman.
-
-
2 pull requests merged.
-
Add CHANGES.md describing changes after the first Origin Trial w3c/window-management#39.
-
Update the Explainer's proposed API shape to address recent feedback w3c/window-management#37.
-
-
2 pull requests received 18 new comments.
-
Update the Explainer's proposed API shape to address recent feedback w3c/window-management#37 (16 comments by @kenchris, @michaelwasserman, @pwnall)
-
Add CHANGES.md describing changes after the first Origin Trial w3c/window-management#39 (2 comments by @michaelwasserman, @tomayac)
-
w3c/openscreenprotocol
-
1 issue opened.
-
[meta] Publish First Public Working Draft w3c/openscreenprotocol#249, by @anssiko.
-
-
1 issue closed.
-
[question] Are there any receiver application in the wild? w3c/openscreenprotocol#243.
-
-
12 issues received 20 new comments.
-
[question] Are there any receiver application in the wild? w3c/openscreenprotocol#243 (5 comments by @jimmywarting, @markafoltz, @rektide)
-
[Remote Playback] Capabilities for HDR rendering and display w3c/openscreenprotocol#194 (2 comments by @anssiko, @markafoltz)
-
Add a back pressure signal for media remoting w3c/openscreenprotocol#241 (2 comments by @anssiko, @markafoltz)
-
Determine if there is an advantage to session resumption outside of early data. w3c/openscreenprotocol#220 (2 comments by @markafoltz)
-
[Remote Playback] Refinements to Remote Playback protocol w3c/openscreenprotocol#159 (1 comment by @markafoltz)
-
Adjust cipher and signature algorithm preference list for hardware w3c/openscreenprotocol#218 (1 comment by @markafoltz)
-
Do agents need to support the Cookies extension (used in HelloRetryRequest)? w3c/openscreenprotocol#219 (1 comment by @markafoltz)
-
Update SPAKE2 section according to current IETF draft w3c/openscreenprotocol#235 (1 comment by @markafoltz)
-
-
4 pull requests opened.
-
Adds a backpressure signal to the streaming protocol. w3c/openscreenprotocol#248, by @markafoltz.
-
Editorial: fix reference to CDDL. w3c/openscreenprotocol#247, by @markafoltz.
-
Attempt to fix travis-ci w3c/openscreenprotocol#246, by @markafoltz.
-
Fix a typo and dfn autolink w3c/openscreenprotocol#245, by @anssiko.
-
-
3 pull requests merged.
-
Editorial: fix reference to CDDL. w3c/openscreenprotocol#247.
-
Fix a typo and dfn autolink w3c/openscreenprotocol#245.
-
Attempt to fix travis-ci w3c/openscreenprotocol#246.
-
-
1 pull request received 1 new comment.
w3c/remote-playback
-
2 issues received 2 new comments.
-
RemotePlaybackState enum can become misleading when changing media.src w3c/remote-playback#125 (1 comment by @markafoltz)
-
1 pull request opened.
-
Allow remote playback device to choose the remote playback source. w3c/remote-playback#141, by @markafoltz.
-
-
3 pull requests merged.
-
Editorial: simplify spec by using new features in ReSpec w3c/remote-playback#135.
-
Editorial: Align with Web IDL specification w3c/remote-playback#138.
-
Editorial: Use "group" respec config w3c/remote-playback#140.
-
-
4 pull requests received 13 new comments.
-
Allow remote playback device to choose the remote playback source. w3c/remote-playback#141 (10 comments by @baylesj, @jernoble, @markafoltz, @mounirlamouri)
-
Editorial: simplify spec by using new features in ReSpec w3c/remote-playback#135 (1 comment by @markafoltz)
-
w3c/secondscreen-wg
-
1 issue received 2 new comments.
-
Second Screen WG/CG - TPAC 2020 agenda w3c/secondscreen-wg#1 (2 comments by @anssiko, @michaelwasserman)
-
GitHub
w3c/remote-playback
-
1 issue opened.
-
A w3c/remote-playback#139, by @quile90958.
-
-
1 issue closed.
-
A w3c/remote-playback#139.
-
-
1 pull request opened.
-
Editorial: Use "group" respec config w3c/remote-playback#140, by @tidoust.
-
-
1 pull request merged.
-
Editorial: use ES6 for example code w3c/remote-playback#136.
-
-
1 pull request received 1 new comment.
w3c/presentation-api
-
1 pull request opened.
-
Editorial: fix link to Navigator and update Respec URL w3c/presentation-api#483, by @tidoust.
-
-
1 pull request received 1 new comment.
w3c/window-management
-
7 issues opened.
-
Find out how to integrate with Visual Viewport w3c/window-management#36, by @kenchris.
-
Integrate with Window Segmentation API w3c/window-management#35, by @kenchris.
-
`primary` vs `isPrimary` w3c/window-management#32, by @jakearchibald.
-
Should `touchSupport` be `pointerTypes`? w3c/window-management#31, by @jakearchibald.
-
Putting the event target behind a permission w3c/window-management#30, by @jakearchibald.
-
Why `scaleFactor` and not `devicePixelRatio`? w3c/window-management#29, by @jakearchibald.
-
Should `onscreenschange` provide useful data? w3c/window-management#28, by @tomayac.
-
-
1 issue closed.
-
`primary` vs `isPrimary` w3c/window-management#32.
-
-
7 issues received 47 new comments.
-
Putting the event target behind a permission w3c/window-management#30 (35 comments by @inexorabletash, @jakearchibald, @kenchris, @michaelwasserman)
-
Why `scaleFactor` and not `devicePixelRatio`? w3c/window-management#29 (3 comments by @jakearchibald, @kenchris, @michaelwasserman)
-
Integrate with Window Segmentation API w3c/window-management#35 (3 comments by @anssiko, @kenchris, @michaelwasserman)
-
Should `onscreenschange` provide useful data? w3c/window-management#28 (2 comments by @michaelwasserman, @tomayac)
-
-
3 pull requests opened.
-
Rename ScreenInfo.primary to ScreenInfo.isPrimary w3c/window-management#34, by @michaelwasserman.
-
Update README.md w3c/window-management#33, by @michaelwasserman.
-
-
2 pull requests merged.
-
Rename ScreenInfo.primary to ScreenInfo.isPrimary w3c/window-management#34.
-
Typo fix w3c/window-management#27.
-
-
1 pull request closed.
-
Update README.md w3c/window-management#33.
-
w3c/openscreenprotocol
-
1 issue opened.
-
TPAC October 2020 topics w3c/openscreenprotocol#244, by @rektide.
-
w3c/secondscreen-wg
-
1 issue received 2 new comments.
GitHub
w3c/secondscreen-wg
-
1 issue opened.
-
Second Screen WG/CG - TPAC 2020 agenda w3c/secondscreen-wg#1, by @anssiko.
-
-
1 issue received 3 new comments.
-
Second Screen WG/CG - TPAC 2020 agenda w3c/secondscreen-wg#1 (3 comments by @anssiko, @louaybassbouss)
-
w3c/window-management
-
1 issue opened.
-
Explain how this is related to the Foldables proposal w3c/window-management#21, by @tomayac.
-
-
1 issue received 2 new comments.
-
Explain how this is related to the Foldables proposal w3c/window-management#21 (2 comments by @kenchris, @plinss)
-
-
5 pull requests opened.
-
Update bikeshed metadata, WG->CG w3c/window-management#26, by @anssiko.
-
Update README.md to point to the draft spec w3c/window-management#25, by @michaelwasserman.
-
Update logo.svg w3c/window-management#24, by @inexorabletash.
-
Add config file to enable PR Preview w3c/window-management#23, by @tidoust.
-
Initial spec skeleton w3c/window-management#22, by @inexorabletash.
-
-
5 pull requests merged.
-
Update bikeshed metadata, WG->CG w3c/window-management#26.
-
Update README.md to point to the draft spec w3c/window-management#25.
-
Update logo.svg w3c/window-management#24.
-
Add config file to enable PR Preview w3c/window-management#23.
-
Initial spec skeleton w3c/window-management#22.
-
-
2 pull requests received 5 new comments.
-
Update bikeshed metadata, WG->CG w3c/window-management#26 (4 comments by @anssiko, @inexorabletash, @pwnall)
-
w3c/presentation-api
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/presentation-api#482, by @autokagami.
-
w3c/remote-playback
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/remote-playback#138, by @autokagami.
-
GitHub
w3c/window-management
-
2 issues opened.
-
Request to track the "active" screen w3c/window-management#17, by @michaelwasserman.
-
HDR / WCG w3c/window-management#20, by @jimbankoski.
-
-
1 issue closed.
-
Scope of the initial proposal w3c/window-management#15.
-
-
5 issues received 16 new comments.
-
HDR / WCG w3c/window-management#20 (8 comments by @chrisn, @Garbee, @jimbankoski, @michaelwasserman, @ThomasTheDane)
-
Reuse existing Screen interface or add something new? w3c/window-management#18 (3 comments by @kenchris, @michaelwasserman)
-
Scope of the initial proposal w3c/window-management#15 (3 comments by @hober, @MichaelKetting, @michaelwasserman)
-
Specify the order of returned screen objects w3c/window-management#19 (1 comment by @michaelwasserman)
-
-
1 pull request opened.
-
Combine Window Placement and Screen Enumeration documents w3c/window-management#16, by @michaelwasserman.
-
-
1 pull request merged.
-
Combine Window Placement and Screen Enumeration documents w3c/window-management#16.
-
-
1 pull request received 74 new comments.
-
Combine Window Placement and Screen Enumeration documents w3c/window-management#16 (74 comments by @michaelwasserman, @pwnall)
-
w3c/presentation-api
-
1 pull request opened.
-
Fix some HTML tidy formatting w3c/presentation-api#481, by @markafoltz.
-
-
1 pull request merged.
-
Fix some HTML tidy formatting w3c/presentation-api#481.
-
-
1 pull request received 1 new comment.
GitHub
w3c/window-management
-
7 issues opened.
-
Scope of the initial proposal w3c/window-management#15, by @michaelwasserman.
-
Specify the order of returned screen objects w3c/window-management#19, by @michaelwasserman.
-
Reuse existing Screen interface or add something new? w3c/window-management#18, by @michaelwasserman.
-
EXPLAINER typo: eluded -> alluded w3c/window-management#14, by @inexorabletash.
-
FullscreenOptions `screen` member should not be nullable w3c/window-management#13, by @domenic.
-
screenschange is easy to mistake for screenchange w3c/window-management#12, by @kenchris.
-
Simplify JS w3c/window-management#11, by @kenchris.
-
-
3 issues closed.
-
Simplify JS w3c/window-management#11.
-
EXPLAINER typo: eluded -> alluded w3c/window-management#14.
-
FullscreenOptions `screen` member should not be nullable w3c/window-management#13.
-
-
8 issues received 11 new comments.
-
FullscreenOptions `screen` member should not be nullable w3c/window-management#13 (2 comments by @inexorabletash, @michaelwasserman)
-
allow window minimize & restore (focus) w3c/window-management#3 (2 comments by @michaelwasserman, @nadavsinai)
-
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)
w3c/presentation-api
-
1 pull request received 3 new comments.
-
Add support for allowing same-screen display w3c/presentation-api#479 (3 comments by @dlibby-, @takumif)
-
GitHub
w3c/openscreenprotocol
-
1 issue opened.
-
[question] Are there any receiver application in the wild? w3c/openscreenprotocol#243, by @jimmywarting.
-
w3c/presentation-api
-
1 issue opened.
-
reconnect after termination w3c/presentation-api#480, by @jimmywarting.
-
-
1 issue received 1 new comment.
-
Can the same browsing context act as a controller and receiver? w3c/presentation-api#338 (1 comment by @jimmywarting)
-
-
1 pull request opened.
-
Add support for allowing same-screen display w3c/presentation-api#479, by @dlibby-.
-
-
1 pull request received 1 new comment.
w3c/remote-playback
-
1 issue opened.
-
Export terms w3c/remote-playback#137, by @hober.
-
-
2 issues received 3 new comments.
GitHub
w3c/presentation-api
-
2 issues opened.
-
HTTP header customization when fetching the presentation page w3c/presentation-api#478, by @markafoltz.
-
Requesting enhancements to the presentation API w3c/presentation-api#477, by @rdrrichards.
-
w3c/remote-playback
-
1 issue received 3 new comments.
-
Remote Playback API tests and implementation report w3c/remote-playback#92 (3 comments by @anssiko, @Honry, @mounirlamouri)
-
-
2 pull requests opened.
-
Editorial: use ES6 for example code w3c/remote-playback#136, by @Honry.
-
Editorial: simplify spec by using new features in ReSpec w3c/remote-playback#135, by @Honry.
-
-
1 pull request merged.
-
Editorial: clean up Dependencies section w3c/remote-playback#134.
-
-
1 pull request closed.
-
Editorial: use modern features of ReSpec w3c/remote-playback#133.
-
-
3 pull requests received 8 new comments.
-
Editorial: clean up Dependencies section w3c/remote-playback#134 (4 comments by @anssiko, @Honry, @mounirlamouri)
-
Editorial: simplify spec by using new features in ReSpec w3c/remote-playback#135 (3 comments by @Honry, @mounirlamouri)
-
GitHub
w3c/remote-playback
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Editorial: clean up Dependencies section w3c/remote-playback#134, by @Honry.
-
Editorial: use modern features of ReSpec w3c/remote-playback#133, by @Honry.
-
-
2 pull requests received 5 new comments.
-
Editorial: use modern features of ReSpec w3c/remote-playback#133 (4 comments by @anssiko, @Honry, @mounirlamouri)
-
w3c/presentation-api
-
1 issue opened.
-
Same-screen presentation w3c/presentation-api#476, by @dlibby-.
-
-
1 issue received 8 new comments.
-
Same-screen presentation w3c/presentation-api#476 (8 comments by @anssiko, @dlibby-, @markafoltz, @tidoust)
-
w3c/openscreenprotocol
-
1 issue opened.
-
[Meta] Track CFRG PAKE competition outcome w3c/openscreenprotocol#242, by @markafoltz.
-
Participants
-
2 participants joined.
-
Daniel Libby (Microsoft Corporation) joined.
-
Zouhir Chahoud (Microsoft Corporation) joined.
-
-
1 organization joined.
-
Microsoft Corporation joined.
-
GitHub
w3c/remote-playback
-
1 issue received 2 new comments.
-
Remote Playback API tests and implementation report w3c/remote-playback#92 (2 comments by @anssiko, @Honry)
-
Participants
-
3 participants joined.
-
Mark Watson (Netflix Inc.) joined.
-
Takumi Fujimoto (Google LLC) joined.
-
Brandon Tolsch (Google LLC) joined.
-
-
19 participants left.
-
Zhiqiang Zhang (Alibaba Group) left.
-
Dongwoo Joshua Im (Samsung Electronics Co., Ltd.) left.
-
Youngsun Ryu (Samsung Electronics Co., Ltd.) left.
-
Wonsuk Lee (Electronics and Telecommunications Research Institute (ETRI)) left.
-
Hongki Cha (Electronics and Telecommunications Research Institute (ETRI)) left.
-
Jean-Claude Dufourd (Institut Mines-Télécom) left.
-
Yukinori Endo (Mitsubishi Electric Corporation) left.
-
Jonathan Jeon (Electronics and Telecommunications Research Institute (ETRI)) left.
-
Mark Watson (Netflix Inc.) left.
-
Noriya Sakamoto (Toshiba Corporation) left.
-
Min Ren (Tencent) left.
-
Hiroyuki Aizu (Toshiba Corporation) left.
-
Raphaël Troncy (Institut Mines-Télécom) left.
-
Bob Lund (Cable Television Laboratories Inc) left.
-
Anton Vayvod (Google LLC) left.
-
Nicolas Dossou-Gbete (Google LLC) left.
-
Alexander Taboriskiy (Google LLC) left.
-
Peter Thatcher (Google LLC) left.
-
Takumi Fujimoto (Google LLC) left.
-
-
6 organizations joined.
-
Netflix Inc. joined.
-
SPORTTOTAL AG joined.
-
LG Electronics joined.
-
Google LLC joined.
-
Espial Group Inc. joined.
-
British Broadcasting Corporation joined.
-
GitHub
w3c/openscreenprotocol
-
2 issues opened.
-
Add a back pressure signal for media remoting w3c/openscreenprotocol#241, by @takumif.
-
WebRTC/media-streaming with Presentation API? w3c/openscreenprotocol#240, by @rektide.
-
w3c/remote-playback
-
1 issue opened.
-
Allow adapting the bitrate to network/receiver constraints when using MSE w3c/remote-playback#132, by @takumif.
-
-
5 issues closed.
-
Define remote playback interaction with background playback policies w3c/remote-playback#118.
-
Interoperability concerns by lack of a common denominator in transport w3c/remote-playback#74.
-
How does remote playback interact with EME? w3c/remote-playback#124.
-
Explore polyfilling Remote Playback API on top of Presentation API w3c/remote-playback#119.
-
Support for TTML and IMSC captions w3c/remote-playback#120.
-
-
1 issue reopened.
-
Reconnecting media elements to the playback w3c/remote-playback#5, by @markafoltz.
-
-
9 issues received 24 new comments.
-
RemotePlaybackState enum can become misleading when changing media.src w3c/remote-playback#125 (7 comments by @jernoble, @mounirlamouri)
-
Remote Playback API tests and implementation report w3c/remote-playback#92 (5 comments by @anssiko, @Honry, @mounirlamouri, @tidoust)
-
Reconnecting media elements to the playback w3c/remote-playback#5 (4 comments by @anssiko, @markafoltz, @mounirlamouri)
-
Define remote playback interaction with background playback policies w3c/remote-playback#118 (2 comments by @markafoltz, @mounirlamouri)
-
Interoperability concerns by lack of a common denominator in transport w3c/remote-playback#74 (2 comments by @markafoltz, @mounirlamouri)
-
Explore polyfilling Remote Playback API on top of Presentation API w3c/remote-playback#119 (1 comment by @mounirlamouri)
-
-
1 pull request opened.
-
Add note about playback policies. w3c/remote-playback#131, by @markafoltz.
-
-
1 pull request merged.
-
Add note about playback policies. w3c/remote-playback#131.
-
-
1 pull request closed.
-
Add a remoting buffer state attribute to RemotePlayback w3c/remote-playback#126.
-
-
2 pull requests received 7 new comments.
-
Add note about playback policies. w3c/remote-playback#131 (5 comments by @markafoltz, @mounirlamouri)
-
Add a remoting buffer state attribute to RemotePlayback w3c/remote-playback#126 (2 comments by @mounirlamouri, @takumif)
-
w3c/window-management
-
2 issues opened.
-
Additional ability for window to stay on top of other windows w3c/window-management#10, by @ThomasTheDane.
-
Feature detection support? w3c/window-management#9, by @michaelwasserman.
-
-
2 issues received 2 new comments.
-
Additional ability for window to stay on top of other windows w3c/window-management#10 (1 comment by @Garbee)
-