Currently, speaker resets to off on every reload, unlike microphone which remembers its state.
Suggestion: Persist speaker setting like microphone.
Thanks!
Currently, speaker resets to off on every reload, unlike microphone which remembers its state.
Suggestion: Persist speaker setting like microphone.
Thanks!
It is restricted by the browser's security policy and cannot be automatically enabled; it must be manually enabled each time.
Thanks for the quick response.
You are right that modern browsers enforce strict autoplay policies and audio cannot start fully automatically without prior user permission.
That said, once a user grants autoplay permission for a specific site, for example, in Chrome via chrome://settings/content/sound the audio stream will start automatically on every subsequent page load or reload. No manual toggle is required. The JetKVM dev build already behaves this way for audio. ( GitHub - pennycoders/kvm at feat/audio-support )
Since microphone permissions already persist in this manner, could we apply the same approach to speaker audio?
Proposed feature approach:
Store the users last speaker preference in localStorage
On page load, if the speaker is enabled, attempt to start the audio track automatically
If autoplay is blocked, display a clear prompt with direct links to the browsers sound/autoplay settings so the user can enable it
Thoughts?