[w3ctag/design-reviews] <usermedia> element (part of PEPC) (Issue #1218)

tungnh28 created an issue (w3ctag/design-reviews#1218)

### Specification

https://github.com/w3c/mediacapture-extensions/compare/main...otherdaniel:mediacapture-extensions:usermedia-element

### Explainer

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

### Links

- The WG's request for this TAG review: https://  <!-- If the WG didn't express consensus to ask the TAG for a review, use the "Other Specification Review" template instead, at https://github.com/w3ctag/design-reviews/issues/new?template=015-other-spec-review.yaml. This is usually a deep link into minutes or an email thread. -->
- Previous early design review, if any: https://github.com/w3ctag/design-reviews/issues/####
- An introduction to the feature, aimed at unfamiliar audiences: https://  <!-- Can be the specification's or explainer's introduction, or another section. -->
- A description of the problems that end-users were facing before this proposal: https://  <!-- See https://w3ctag.github.io/explainer-explainer/#end-user-need -->
- Alternatives considered: https://  <!-- See https://w3ctag.github.io/explainer-explainer/#alternatives -->
- Examples of how to use the proposal to solve the end-users' problems: https://  <!-- See https://w3ctag.github.io/explainer-explainer/#describe-proposal -->
- What do the end-users experience with this proposal: https://  <!-- See https://w3ctag.github.io/explainer-explainer/#describe-proposal -->
- User research you did to validate the problem and/or design, if any: https://
- Web Platform Tests:  <!-- Or other tests if this is not a web platform feature. -->


### The specification

- [x] Follows the [Web Platform Design Principles](https://www.w3.org/TR/design-principles/).
- [ ] Includes Security and Privacy Considerations sections based on answers to the [Security/Privacy Questionnaire](https://www.w3.org/TR/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](http://www.w3.org/2011/04/webrtc/) Working Group.
- Group intended to standardize this work: - Same
- Incubation and standards groups that have discussed the design:
  - [WebAppSec 2025](https://github.com/w3c/webappsec/blob/main/meetings/2025/2025-10-15-minutes.md)
  - https://github.com/WICG/PEPC/issues/62
  - [TPAC 2024](https://www.w3.org/2024/09/breakouts/minutes-18.html)
  - Breakouts planned at TPAC 2025
  - WebRTC WG and editor's [meeting 2025-2026](https://docs.google.com/document/d/1-zcZ5RLJhL15sOTP00hhYc_mXMD8ObxGsMB28sNG1t8/edit?tab=t.0#heading=h.ofxmlqshc978)
  

### 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
    

### You should also know that...

- Historical context: This is a subsequence step of `[<permission>](https://github.com/w3ctag/design-reviews/issues/1079)` 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>`](https://github.com/w3ctag/design-reviews/issues/1140) 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 draft specification is currently hosted in a personal repository and has not yet been submitted as a formal pull request, we intend to request a review from the WebRT's [media capture extensions](https://github.com/w3c/mediacapture-extensions) soon.

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

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


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1218
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1218@github.com>