New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify when to fire devicechange event for changes of device capabilities #730
Comments
Devices can be added and removed. Plug and play USB devices, Bluetooth devices, virtual devices. Firing |
The issue is Chromium refuses to list or capture audio devices that include monitor text in device description at Linux. To workaround that arbitrary restriction it is possible to dynamically change and set the devices being captured to a monitor device https://bugs.chromium.org/p/chromium/issues/detail?id=931749, thus, when the device changes not only must a |
I think we have to be careful not to disturb what I think is the primary use case of
Recall: the event is insufficient, apps must diff Hopefully apps are diffing only on |
Not clear how properties such as label would change, or whether browsers would be able to detect it (apart from polling). |
This seems like a user agent configuration issue, and it's not clear there's value in standardizing what they should do here. Closing as no action needed. |
Devices may not be added or removed but their capabilities or labels may changed.
In that case, it might be good to fire a devicechange event provided labels are exposed.
The text was updated successfully, but these errors were encountered: