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 issue on 250ms file #6

Open
lcherone opened this issue Mar 22, 2019 · 1 comment
Open

Chrome issue on 250ms file #6

lcherone opened this issue Mar 22, 2019 · 1 comment

Comments

@lcherone
Copy link

lcherone commented Mar 22, 2019

In chrome im getting the following error, file is served though express (static route)

Resource interpreted as Document but transferred with MIME type audio/mpeg: "http://127.0.0.1:8080/assets/sounds/silence.mp3".

When you hit the file directly it will work, but not in an audio tag.

Are these files just headers with no data? And its basically seen by chrome as corrupt.

Geeze I just need to autoplay a bell in chrome via js without clicking lol im getting defeated by 3 lines of code lol

@rawr51919
Copy link

In chrome im getting the following error, file is served though express (static route)

Resource interpreted as Document but transferred with MIME type audio/mpeg: "http://127.0.0.1:8080/assets/sounds/silence.mp3".

When you hit the file directly it will work, but not in an audio tag.

Are these files just headers with no data? And its basically seen by chrome as corrupt.

Geeze I just need to autoplay a bell in chrome via js without clicking lol im getting defeated by 3 lines of code lol

may have to override the header for that file to be the proper one so it'll play, dirty hack yet it might work :)

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

No branches or pull requests

2 participants