July 1, 2026

Mic drop… or browser power grab?

The <Usermedia> HTML Element

Chrome’s new camera button is here, and the comments are already screaming ‘new IE’

TLDR: Chrome 151 is adding a built-in web button for camera and mic access that aims to make permissions easier and reduce user mistakes. Supporters like the simpler flow, but commenters are loudly arguing over privacy fears, browser dominance, and whether Chrome is trying to make its own rules for the web.

Google is rolling out a new web page button called <usermedia>, meant to make camera and microphone access feel less like a sketchy pop-up ambush and more like a clear, tap-to-consent moment. In plain English: instead of websites firing off confusing permission requests, the browser shows a built-in control users click themselves. Google says this helps people recover if they accidentally blocked access before, and the company brought receipts: Cisco, Zoom, and Google Meet all reported fewer “why isn’t my mic working?” disasters and better recovery rates.

But the comments? Absolutely not calm. One camp sees a cleaner, safer way to stop those annoying permission dead ends. The other sees Chrome flexing its muscles again and quietly inventing the future of the web by itself. The hottest accusation was that Chrome is turning into the “new IE”—a reference to the bad old days when one dominant browser pushed everyone else around. Critics also asked the obvious question: why invent a shiny new page element at all when the old camera-access system could maybe just be fixed to work better after a user click?

And of course, the paranoia jokes arrived right on schedule. One commenter deadpanned about what new thing they’ll have to block so they can’t be fingerprinted, while another dropped a dripping-with-sarcasm “This won’t get abused. /s.” So yes, Google says this is about less boilerplate and fewer broken calls. The crowd says it’s also about power, privacy, and whether the web is getting cleaner—or just weirder.

Key Points

  • The article says Chrome 151 will introduce the <usermedia> HTML element for camera and microphone access as part of the Capability Elements suite.
  • Capability Elements are described as replacing the earlier generic <permission> proposal with specialized, data-mediating controls such as <geolocation> and <usermedia>.
  • <usermedia> is designed to capture user intent, trigger browser-managed prompts, and provide a MediaStream directly to applications without separate getUserMedia() calls.
  • The article cites origin-trial results from Cisco, Zoom, and Google Meet showing higher permission recovery rates and fewer media capture errors.
  • The element is presented as solving the browser 'permission hole' by enabling on-page recovery after a user has previously denied camera or microphone access.

Hottest takes

“This won’t get abused. /s” — rho138
“becomes the new IE” — phantomathkg
“Anything new I have to block so my ass can’t be fingerprinted?” — felooboolooomba
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.
The <Usermedia> HTML Element - Weaving News | Weaving News