Closed Bug 782137 Opened 13 years ago Closed 13 years ago

mozGetUserMedia doesn't consistently return the same object type for pictures vs. audio/video

Categories

(Core :: WebRTC: Audio/Video, defect)

Product:
Core
Component:
WebRTC: Audio/Video
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: jsmith, Unassigned)

Details

Steps: 1. Call mozGetUserMedia with {picture: true} in the first argument with a valid success and error callback 2. Inspect the results of the stream object returned in the success callback Expected: The object type should be a LocalMediaStream object type. Actual: A File object type is returned instead. This is problematic - the API right now returns two very different object types with inconsistencies in how they are used, and this violates the spec. We should be consistent in what object type is returned.
Whiteboard: [getUserMedia]
Summary: Calling mozGetUserMedia with {picture: true} - wrong Object Type is returned → mozGetUserMedia doesn't consistently return the same object type for pictures vs. audio/video
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Whiteboard: [getUserMedia]
You need to log in before you can comment on or make changes to this bug.