W3C home > Mailing lists > Public > public-media-capture@w3.org > July 2016

[mediacapture-main] Should devicechange fire once or twice when I insert a USB cam with mic?

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Fri, 22 Jul 2016 15:12:11 +0000
To: public-media-capture@w3.org
Message-ID: <issues.opened-167067353-1469200330-sysbot+gh@w3.org>
jan-ivar has just created a new issue for 

== Should devicechange fire once or twice when I insert a USB cam with
 mic? ==
The spec appears conflicted on this:

 it says: *"[Fired when] the set of media devices, available to the 
User Agent, has changed."*

i.e. when the ***set*** changes. This seems to allow an implementation
 to add a cam and a mic to the ***set*** and fire 1 event.

 it says:

*"When a new media input or output device is made available, and if 
the permission state of the "list-devices" permission is "granted", 
the User Agent MUST queue a task that fires a simple event named 
devicechange at the MediaDevices object. These events are potentially 
triggered simultaneously across browsing contexts on different 
origins; user agents can add fuzzing on the timing of events to avoid 
cross-origin activity correlation."*

... which seems to normatively dictate two events when e.g. I insert 
my Logitech camera which has both a camera and a microphone on it.

Oddly, the same paragraph allows for time-shifting, so there's 
apparently no urgency in firing these events, so the sole purpose of 
firing two events would seem to satisfy someone who is counting device
 additions and removals (which seems like a poor reason, given that 
you won't know whether it was an addition or a removal without 
comparing the list against a previous pull of the list, at which point
 you'd be able to cope with multiples as well).

Was this our intent, and is this the best behavior? We seem to use the
 term "device" loosely, so my guess is no. I vote we allow 
implementations to optimize here and fire one event in this case.

Please view or discuss this issue at 
https://github.com/w3c/mediacapture-main/issues/375 using your GitHub 
Received on Friday, 22 July 2016 15:12:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:36 UTC