Over the last weeks, the @w3c #WebRTC Working Group released two first public working drafts of new #APIs to help with improved screen-sharing capabilities in Web apps #timetogiveinput
1
3
2
The first API, Capture Handle Identity, provides a mechanism for a Web #app (e.g. videoconf) capturing the content of another one (e.g. slide deck) to collaborate => the users sharing their screen can navigate slides from within the videoconf tool w3.org/TR/capture-handle-ide…
1
This is done by letting the captured Web #app expose info to the capturing one to allow the two apps to collaborate. Read this explainer that lists more use cases as well as sample code: github.com/w3c/mediacapture-…
1
This #API is shipping in #Chrome 102, which allows running the following demos: w3c.github.io/mediacapture-h…
1
1
As always, the work is happening in a #github repo, where a complementary work to describe generically affordances a captured app may expose to its capturer is also investigated:
github.com/w3c/mediacapture-…
1
The limit of videoconferencing systems to a single screen share is a choice of these systems vendors (probably because screen content often requires to be close to fullscreen to be readable) - #WebRTC has no such restriction.
How would concurrent screen shares be used?
Jun 2, 2022 · 10:36 AM UTC
1

