Bugzilla

(In reply to Bodea Daniel [:danibodea] from comment #9)
> And ALSO OCCURS on Chrome, so it might be a website issue.

Yes, it is up to the website to determine what should happen in this case. The track of a disconnected microphone [ends](https://w3c.github.io/mediacapture-main/getusermedia.html#track-ended), which is a permanent state in the spec.

Resumption of capture on reinsertion is not automatic in browsers, and requires an act by the web site instead., e.g. by listening to the `devicechange` event and calling `getUserMedia` again.

Here's a [headset detection example](https://jsfiddle.net/jib1/yohgar95/show).

(In reply to Bodea Daniel [:danibodea] from comment #9)
> And ALSO OCCURS on Chrome, so it might be a website issue.

Yes, it is up to the website to determine what should happen in this case. The track of a disconnected microphone [ends](https://w3c.github.io/mediacapture-main/getusermedia.html#track-ended), which is a permanent state in the spec.

Resumption of capture on reinsertion is not automatic in browsers, and requires an act by the web site instead, e.g. by listening to the `devicechange` event and calling `getUserMedia` again.

Here's a [headset detection example](https://jsfiddle.net/jib1/yohgar95/show).

(In reply to Bodea Daniel [:danibodea] from comment #9)
> And ALSO OCCURS on Chrome, so it might be a website issue.

Yes, it is up to the website to determine what should happen in this case. The track of a disconnected microphone [ends](https://w3c.github.io/mediacapture-main/getusermedia.html#track-ended), which is a permanent state in the spec.

Resumption of capture on reinsertion is not automatic in browsers, and requires an act by the web site instead, e.g. by listening to the `devicechange` event and calling `getUserMedia` again.

Here's a [headset detection example](https://jsfiddle.net/jib1/yohgar95/show) (try connecting and disconnecting a headset with it).