- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 Jan 2024 13:57:08 +0000
- To: public-webrtc-logs@w3.org
> The current plan is to use `Promise<undefined> MediaSession.setMicrophoneActive` which could return different errors or error types. This is one place where different mute reasons could be surfaced. Other places might be the togglemicrophone action handler dictionary, or MediaStreamTrack like suggested above. > > That said, as it is right now, togglemicrophone would provide a boolean value to muted tracks that we thought might be sufficient in the short term. Hence why I would not concentrate on this topic right now. > > Instead, I'd like to first validate that this minimal MediaSession API is good enough: > > * It should allow websites like Google Meet to fix the double mute issue, whether mute can fire only for this reason or for other reasons like in Chrome > * It should be extensible to support more advanced cases we want to tackle in the future (multiple microphone capture...) What is the right place to discuss the Media Session proposal? It looks like a potential way forward, assuming it supports having a per-device state. -- GitHub Notification of comment by guidou Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1916909076 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 30 January 2024 13:57:10 UTC