- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Dec 2019 16:19:57 +0000
- To: public-webrtc-logs@w3.org
If the user is not interacting/interested in the web application, the application is probably not in a position to select the proper means to request user interest. For instance, you might want the device to vibrate instead of playing a ring tone if the device is in vibration mode, but you probably do not want to let the application know you are in vibration mode. This API does not seem to be a good fit for this use case, which is closer to existing notification API use cases. On the other hand, if the web application knows the user is interacting with the page, like in the middle of a phone call, it seems natural to use the same speaker device. I agree though that there are use cases for multi speaker setup cases (hence why HTMLMediaElement.setSinkId is good to have too). These use cases might not be as common, hence why it might be useful to have a page-wide version. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-output/issues/87#issuecomment-560467558 using your GitHub account
Received on Monday, 2 December 2019 16:19:59 UTC