Repro tool for the Windows OS camera prompt issue tracked in
OPS-7378
(camera prompt on signing into claude.ai / linkedin.com / youtube.com). The
content-scope-scripts deviceEnumerationFix only intercepts
MediaDevices.enumerateDevices(); this page also exercises every adjacent API
(getUserMedia, permissions.query, RTCPeerConnection,
getDisplayMedia, iframe contexts) so a tester can isolate exactly which call still
triggers the OS prompt on a build under test.
How to use it. On a fresh Windows install where camera permission has never been granted or denied for the DuckDuckGo app, run each technique one at a time, watch for the native OS camera prompt, and use the "OS prompt?" dropdown next to each row to record what you observed. When done, hit Download results to export a JSON record.
Note: the B group calls getUserMedia directly and so will legitimately surface a camera/mic prompt on any browser. The question for this repro is whether
those calls surface the native Windows OS prompt in addition to or instead of the
in-app permission UI.