The HTML Element
Key takeaways
- Available from Chrome 151, this element marks the next phase of the transition from generic permission requests to targeted and functional controls for accessing camera and microphone streams.
- The <usermedia> element is the next specialized control to launch in the Capability Elements suite, following the successful introduction of <geolocation>.
- The <geolocation> element provides a location object to your site, and <usermedia> manages the entire flow for camera and microphone access.
Available from Chrome 151, this element marks the next phase of the transition from generic permission requests to targeted and functional controls for accessing camera and microphone streams. By moving away from script-triggered prompts toward a declarative and user-activated experience, <usermedia> reduces boilerplate code, improves security, and provides a seamless recovery path for users who have previously denied access, effectively solving the long-standing permission hole.
The <usermedia> element is the next specialized control to launch in the Capability Elements suite, following the successful introduction of <geolocation>. This transition from the original and generic <permission> proposal—part of the PEPC initiative—lets the browser handle the unique complexities and behaviors of different hardware capabilities more effectively. While the early proposal focused primarily on managing permission states, such as allow versus deny, Capability Elements function as data mediators.
The <geolocation> element provides a location object to your site, and <usermedia> manages the entire flow for camera and microphone access. It captures user intent, manages the browser prompt, and delivers the MediaStream object to the application. This shift eliminates the need for separate getUserMedia() calls, simplifies implementation, and ensures the browser has a trusted signal of the user s intent.