Note: Community Groups are proposed and run by the community. Although W3C hosts these
conversations, the groups do not necessarily represent the views of the W3C Membership or staff.
Chairs, when logged in, may publish draft and final reports. Please see report requirements.
TPAC 2024 is fast upon us, and this year, the Screen Capture Community Group will be holding two meetings:
First meeting (1/2), 24 September 2024, 16:30–18:00 (details): A joint one between the Screen Capture CG and the WebRTC WG. We will cover both new and ongoing topics, including:
New API surfaces to facilitate dynamically switching shared surfaces during a video call.
New API changes to increase the capturing application’s insight into the true resolution of shared surfaces.
Continued discussion of Captured Surface Control (link)
Second meeting (2/2), 27 September 2024, 11:00–12:30 (details): A standalone session for the Screen Capture CG. Unlike our typical meetings, which are usually structured discussions of newly proposed Web APIs, this session will be a free-form discussion on any topics related to screen-sharing that participants bring up. We will intentionally avoid a fixed agenda, but to kick off the conversation, here are some ideas we could discuss:
Capturing a rectangular sub-section of the screen.
Comparison of “media-picker” experiences across various browsers and operating systems, discussing what works and why.
Sharing audio – inconsistencies across surface-types, operating systems and browsers.
Echo cancellation.
The challenges of sharing audio from a multi-window application.
Beyond mere screen-capture; what about remote control? Could this ever be possible on the open Web?
Any other topics participants would like to bring up.
Please don’t hesitate to mail me at [email protected] with any questions you might have, or even just to mention that you’ll be dropping by.
The Element Capture API has entered origin trial in Chrome starting with milestone m121. The trial is scheduled to proceed at least until m126 (inclusive), at which point we plan to either ship the API or extend the trial.
The third meeting of the Screen Capture Community Group will take place on June 26. Depending on your timezone, the meeting will start at 10:00 PST, 13:00 ET, or 19:00 CEST.
You’re all invited to join us through this link: https://meet.google.com/mjw-ruqv-rnr
The agenda is still open – please email [email protected] with any content you would like to present.
Current agenda items include:
Element Capture follow-up (discussion of stacking contexts)
Dynamically switching between sharing tabs, windows and screens
APIs for scrolling and controlling captured tabs from the capturing tab
The second meeting of the Screen Capture Community Group will take place on March 21st. Depending on your timezone, the meeting would start at 09:00 PST, 12:00 ET, or 18:00 CET.
Screen capture is useful in many contexts, such as when delivering presentations, collaborating with remote colleagues, or producing local recordings. The Web Platform offers APIs to that end, allowing Web applications to capture screens, windows or tabs, and allowing the captured media to be manipulated in various productive ways.
The popularity of these APIs, and the ubiquity of the applications that use them, are a testament to the importance of the work that has been done thus far.
Mission
We believe that there is yet more untapped potential in the realm of screen capture. It is our mission to innovate further and unblock additional novel uses of screen capture, creating new business opportunities for developers and enriching the lives of users.
Scope
As part of this charter, the Screen capture Community Group is focusing its activities on producing new screen capture APIs and extending existing ones. APIs directly involving screen capture are in scope, as are APIs that would typically be used in tandem with screen capture.
Work mode
The group will conduct all of its technical work in public, on GitHub repositories, with a supporting mailing list for logistical and administrative purposes.
Meetings will normally be public and open to anyone to join. Should the need arise, meetings may be restricted to Community Group participants and guests invited by the group chairs. In either case, a public summary or minutes will be made available publicly.
This is a community initiative. This group was originally proposed on 2022-12-19 by Elad Alon. The following people supported its creation: Elad Alon, Harald Alvestrand, Francois Beaufort, Tsahi Levent-Levi, Simon Hangl. W3C’s hosting of this group does not imply endorsement of the activities.
![](/cats-d8c4vu/www.w3.org/community/sccg/" method="get" id="adminbarsearch"><input class="adminbar-input" name="s" id="adminbar-search" type="text" value="" maxlength="150" /><label for="adminbar-search" class="screen-reader-text">Search</label><input type="submit" class="adminbar-button" value="Search" /></form></div></li></ul> </div>
</div>
<!--[if lte IE 8 ]>
<noscript><strong>JavaScript is required for this website to be displayed correctly. Please enable JavaScript before
continuing...</strong></noscript>
<![endif]-->
<header>
<div class="logos">
<a href="/" class="w3-logo"><img alt="w3c logo" class="animated fadeInLeft" src="/assets/logos/w3c-2025-transitional/w3c-skew-10-greenish.svg"/></a>
<a href="/community/" class="cgbg-logo"><img alt="w3c community group logo" class="animated fadeInRotate height"
src="/community/wp-content/themes/StoryTeller/img/svg/cgbg-logo.svg"/></a>
<a href="/community/" class="cgbg-logo-title"><h1 class="animated fadeInRight">Community & Business Groups</h1>
</a>
</div>
<div class="white-bar"></div>
<div class="white-circle"></div>
<div class="blue-top"></div>
</header><!-- #header -->
<div class="center ov-visible">
<nav id="access" class="right main-nav">
<ul id="menu-top-menu">
<li id="menu-item-60"
class="cg menu-item menu-item-type-custom menu-item-object-custom current-menu-item menu-item-home menu-item-60">
<a title="Groups" href="/community/groups/"><span>Current Groups</span></a></li>
<li id="menu-item-57" class="rp menu-item menu-item-type-custom menu-item-object-custom menu-item-57"><a
href="/community/reports/"><span>Reports</span></a></li>
<li id="menu-item-59" class="ab menu-item menu-item-type-post_type menu-item-object-page menu-item-59">
<a title="About" href="/community/about/"><span>About</span></a></li>
</ul>
</nav><!-- #access -->
</div>
<div class="center">
<div class="maincolumn">
<div class="breadcrumbs"><ul><li><a href="/community/" title="Community & Business Groups">Home</a> / </li><li>Screen Capture Community Group</li></ul></div>
<section class="group" id="content">
<h2 class="group-title">Screen Capture Community Group</h2>
<div class="intro">
<h2>Background</h2>
<p>Screen capture is useful in many contexts, such as when delivering presentations, collaborating with remote colleagues, or producing local recordings. The Web Platform offers APIs to that end, allowing Web applications to capture screens, windows or tabs, and allowing the captured media to be manipulated in various productive ways.</p>
<p>The popularity of these APIs, and the ubiquity of the applications that use them, are a testament to the importance of the work that has been done thus far.</p>
<h2>Mission</h2>
<p>We believe that there is yet more untapped potential in the realm of screen capture. It is our mission to innovate further and unblock additional novel uses of screen capture, creating new business opportunities for developers and enriching the lives of users.</p>
<h2>Scope</h2>
<p>As part of this charter, the Screen capture Community Group is focusing its activities on producing new screen capture APIs and extending existing ones. APIs directly involving screen capture are in scope, as are APIs that would typically be used in tandem with screen capture.</p>
<h2>Work mode</h2>
<p>The group will conduct all of its technical work in public, on GitHub repositories, with a supporting mailing list for logistical and administrative purposes.</p>
<p>Meetings will normally be public and open to anyone to join. Should the need arise, meetings may be restricted to Community Group participants and guests invited by the group chairs. In either case, a public summary or minutes will be made available publicly.</p>
<h2>Amendments to this charter</h2>
<p>The group chairs can amend the charter.</p>
<a class=repo href=/cats-d8c4vu/github.com/screen-share/><img
src="/cats-d8c4vu/www.w3.org/community/wp-content/themes/StoryTeller/img/svg/github.svg"
alt="" width="15">
screen-share/</a>
<figure>
<figcaption>Group){kind=link}