rationale for getUserMedia on MediaDevices

Resend to correct a typo ---

In the latest version of the draft, there are two ways to call getUserMedia() within the NavigatorUserMedia.

#1:	NavigatorUserMedia.getUserMedia();
#2:	NavigatorUserMedia.MediaDevices.getUserMedia();

Could someone share the rationale why we need the 2nd option?  I couldn't find any spec bug that led to the change.  It seems it also kind of limits future extension of getUserMedia () beyond the media devices.

Best, Shijun

Received on Wednesday, 25 June 2014 16:45:45 UTC