This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the MediaStreamConstraints dictionary, the "video" and "audio" properties already indicate whether the source should be a camera or microphone for the specific MediaTrackConstraints. Having an "sourceType" doesn't give the UA more meaningful instruction, meanwhile, can introduce unnecessary conflict, e.g. by setting the sourceType to "camera" on the "audio" property. Also, typically we should not expect the sourceType to change while applying new constraints on an existing MediaStreamTrack. MediaStreamTrack.kind indicates the sourceType already. There is no clear value keeping the sourceType as constraints in this case either. sourceType "none" is covered by the MediaStreamTrack.radyState, again redundant. Suggest removing sourceType from the constraints list, and mapping the concept to other attributes defined in the spec already.
This property was added with the idea that it could be extended - with, for instance, "file", "screencapture" or others. At the moment, it is not useful. Suggest removing it until we have a real use case for it.
Question sent on the mailing list about removing it on July 4, 2014
Removed sourceType (and SourceTypeEnum) Proposed fix: https://github.com/w3c/mediacapture-main/commit/71f3030cdd686f84bd6decb895d2196c13092bcd