Autoplay Error - Chromium Based Browsers
- John Anderson
Did you know Chromium based browsers, like Google Chrome, require you to interact with the web page before you can hear audio files played? You can read more about why Chrome implemented this auto play policy here: https://developer.chrome.com/blog/autoplay/
At Sharpen, if an end user does not interact with the Sharpen Q page when it first loads, this autoplay restriction will present as a “missed ring” where the user does not hear the ringing sound file being played. You’ll still receive the toast pop-up notifying you of the call, but it will be silent.
To prevent this browser-based block, the user needs to interact with the Sharpen Q page the first time they load it each day. This can be as simple as a left click anywhere on the page (even in blank space) or clicking any of the buttons in the user interface.
Once you’ve interacted with the Sharpen Q page, the browser will allow sound files to be played, including our ringing sound file.
Normally this error message is only present in the console logging of the browser; we’ve surfaced it in a dismissible modal to help the end user understand why they didn’t hear any ringing sound.
We attempted to play a ring sound, but it was automatically muted by your browser. To avoid this issue in the future, you must interact with the Sharpen Q page when it first loads.