Skip to content
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

Chrome 71 event when Chrome autoplay restriction blocks sound #1070

Closed
MalcolmDwyer opened this Issue Nov 9, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@MalcolmDwyer
Copy link

commented Nov 9, 2018

Regarding the upcoming Chrome 71 changes to the autoplay policy, I'm still looking for a way to make Howler tell me when the sound failed to play.

I'm on Chrome 70, but getting 71 behavior by starting up Chrome like this:
(As described here)

$ /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --disable-features=AutoplayIgnoreWebAudio

Here's the behavior:

howlereventsautoplay

I've seen the instructions here, but they don't help because onplayerror never fires. Also mobileAutoEnable true or false makes no difference.

Is there any way to catch the fact that the sound didn't play? Do I need to have onunlock() set a value somewhere, then poll that to check if it was never set?

@ex3ndr

This comment has been minimized.

Copy link

commented Nov 18, 2018

Same here on latest Safari

@goldfire

This comment has been minimized.

Copy link
Owner

commented Dec 10, 2018

Unfortunately, there is currently no way to detect this (I've asked both Google and the Web Audio team). There are some proposals in the works, but nothing solidified just yet. Going to close in favor of #939.

@goldfire goldfire closed this Dec 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.