Specification

https://wicg.github.io/PEPC/usermedia-element-delta.html

Explainer

https://github.com/WICG/PEPC/blob/main/usermedia_element.md, https://github.com/WICG/PEPC/blob/main/explainer.md

Links

• Previous early design review, if any: This is an evolution of work previously reviewed by the TAG.
• An introduction to the feature, aimed at unfamiliar audiences: TLDR.
• A description of the problems that end-users were facing before this proposal: The same core user problem with previous design.
• Alternatives considered: this proposal addresses feedback, to replace the previous design.
• Examples of how to use the proposal to solve the end-users' problems: User journeys.
• What do the end-users experience with this proposal: User journeys.
• User research you did to validate the problem and/or design, if any: a research from the previous TAG review.
• Web Platform Tests: tests.

The specification

• Follows the Web Platform Design Principles.
• Includes Security and Privacy Considerations sections based on answers to the Security/Privacy Questionnaire.

Where and by whom is the work is being done?

• GitHub repo: https://github.com/WICG/PEPC
• Primary contacts:
  • Daniel Vogelheim (@otherdaniel), Google Chrome, Spec Writer
  • Minh Le (@MinhAnhL), Google Chrome, PM
  • Thomas Nguyen (@tungnh), Google Chrome, Engineer
• Organization/project driving the specification: Google Chrome
• This work is being funded by: Google Chrome
• Primary standards group developing this feature: WebRTC Working Group.
• Group intended to standardize this work: WebRTC Working Group.
• Incubation and standards groups that have discussed the design:
  • https://github.com/WICG/PEPC/issues/62
  • TPAC 2024
  • WebAppSec 2025
  • Breakouts planned at TPAC 2025
  • WebRTC WG and editor's meeting 2025-2026

Feedback so far

• Multi-stakeholder feedback:
  • Chromium: Implementing the MVP, the last PEPC OT showed a great improvement for the user experience and granting flow.
  • Mozilla: https://github.com/mozilla/standards-positions/issues/1245, https://github.com/WICG/PEPC/issues/88#issuecomment-3800739616
  • WebKit: Agreed on the initial scope during the WebRTC editor's meeting, and discussions are ongoing to further improve the feature.
  • Developers:
    • https://github.com/WICG/PEPC/issues/62#issuecomment-3786478249
    • https://github.com/WICG/PEPC/issues/2#issuecomment-2393861768
    • https://github.com/WICG/PEPC/issues/2#issuecomment-2393911331
• Major unresolved issues with or opposition to this specification: not available yet
• Status/issue trackers for implementations: Chrome Status

You should also know that...

• Historical context: This is a subsequence step of <permission> element proposal, and in response to feedback and discussions, we are moving away from a single, generic permission element. Instead, we are proposing separate elements tailored to specific capabilities. After splitting and releasing the <geolocation> element proposal, we are now introducing the <usermedia> element. This new element will inherit all attributes, events, and checks from the <permission> element. Ultimately, the <permission> element will function solely as a base class for specialized capability elements and will not be for direct use.
• The specification is currently hosted in a PEPC repository. We intend to request a review from the WebRTC's media capture extensions this week.

<!-- Content below this is maintained by @w3c-tag-bot -->

---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1218