Practice vocabulary for WebRTC media streams: getUserMedia API, MediaStream tracks, muting, screen share, and video element attachment.
0 / 5 completed
1 / 5
The browser JavaScript API used to request access to the user's camera and microphone is called:
The getUserMedia API requests camera/microphone access — the full call is navigator.mediaDevices.getUserMedia({ video: true, audio: true }), which prompts for permission.
2 / 5
The object returned by getUserMedia that contains one or more audio or video sources is called:
The MediaStream contains audio and video tracks — each track (MediaStreamTrack) represents a single source: one for video, one for audio.
3 / 5
When a user clicks the mute button and their audio is silenced without ending the call, this is described as:
The track is muted when the user clicks mute — setting track.enabled = false silences the audio without removing it from the peer connection.
4 / 5
When a user shares their desktop or browser tab during a WebRTC session, this creates:
The screen share creates a display media stream — obtained via navigator.mediaDevices.getDisplayMedia(), it produces a video track of the shared screen.
5 / 5
When a MediaStream is connected to an HTML video element so the user can see the video, this is described as:
The stream is attached to the video element — by setting videoElement.srcObject = stream, the browser renders the MediaStream in the HTML video element.