[FEATURE] Browser pane microphone-block banner reappears and blocks page interaction on every getUserMedia() call

Status Open
Maintainer reply None cached
Activity 0 comments · opened Jul 31, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When a page in the Browser pane calls getUserMedia() (e.g. requesting microphone access), the pane shows a banner: "This page asked for microphone access, which is blocked in the Browser pane. Open the page in your default browser to use it."

<img width="513" height="68" alt="Image" src="https://github.com/user-attachments/assets/b43c0255-9842-42b8-9021-e3be2f5f18b2" />

This is expected behavior — blocking mic access in the sandbox makes sense. However, the banner also blocks the page from updating/rendering until it's manually dismissed, and it reappears every single time the page requests mic access again (e.g. repeated user interaction with a "start microphone" button during iterative testing).

Suggested improvement: keep blocking the actual media access, but either:

don't block page rendering/updates while the banner is shown, or
suppress repeat banners for the same origin/session after the first one, or
make the banner non-modal (dismissible without pausing the page).
This would make it much easier to iteratively test web apps that request microphone/camera access in the Browser pane without needing to manually dismiss the banner after every test cycle.

Proposed Solution

don't block page rendering/updates while the banner is shown, or
suppress repeat banners for the same origin/session after the first one, or
make the banner non-modal (dismissible without pausing the page).
This would make it much easier to iteratively test web apps that request microphone/camera access in the Browser pane without needing to manually dismiss the banner after every test cycle.

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗