- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Apr 2015 15:12:58 +0000
- To: public-media-capture-logs@w3.org
I guess it's there to guard against the steps that follow which dictate device probing in direct response to each enumerateDevices call (a polling model). What's odd is that we now also support 'ondeviceschanged' (a push model), making the obvious place to update any global internal list of devices be right before we fire that event. There's still a reason to build a list uniquely for each (session of an) enumerateDevices call: make the IDs origin-unique, but I'm not sure the amount of CPU needed to do that warrants having the spec optimize around it for us. I feel there's a better way to word this, but it's escaping me at the moment. -- GitHub Notif of comment by jan-ivar See https://github.com/w3c/mediacapture-main/issues/155#issuecomment-90946441
Received on Wednesday, 8 April 2015 15:13:07 UTC