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

Fix for issue #986 handling decodeAudioData events in latest chrome #988

Merged
merged 2 commits into from
Jul 12, 2018
Merged

Fix for issue #986 handling decodeAudioData events in latest chrome #988

merged 2 commits into from
Jul 12, 2018

Conversation

Megabyteceer
Copy link
Contributor

I noticed than decodeAudioData of AudioContext has only one parameter and sometime callback passed in to decodeAudioData dont fire at all. I added checking to handle events via promise syntax in modern browsers.
For me this fix solved problem of frozen preloader which happened randomly.

I noticed than decodeAudioData of AudioContext has only one parameter and sometime callback passed in to decodeAudioData dont fire at all. I added checking to handle events via promise syntax in modern browsers.
For me this fix solved problem of frozen preloader which happened randomly.
@Megabyteceer Megabyteceer changed the title #986 handling decodeAudioData events in latest chrome Fix for issue #986 handling decodeAudioData events in latest chrome Jul 4, 2018
@goldfire goldfire merged commit e862611 into goldfire:master Jul 12, 2018
ringcrl pushed a commit to ringcrl/howler.js that referenced this pull request Apr 21, 2019
Fix for issue goldfire#986 handling decodeAudioData events in latest chrome
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants