Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Bug: Browsers don't respect setting preload to "none" in wavesurfer.load()
See original GitHub issueDemo at http://codepen.io/anon/pen/QdVxbe
Preload is set to none:
wavesurfer.load('https://wavesurfer-js.org/example/split-channels/stereo.mp3', peaks, 'none');
But if you check in “developer tools” the file is clearly loading on page load before the file is played. The DOM shows preload="none" so it is adding the attrbitue.
I understand that preload="none" is only a suggestion to the browser but if I manually add the <audio> element to the page it respects it:
<audio controls preload="none" src="https://wavesurfer-js.org/example/split-channels/stereo.mp3">
Tested under Chrome 55.0.2883.87 and Firefox 51.0.1.
If you can give me an idea what might be causing this I’ll try to fix it.
Issue Analytics
- State:
- Created 7 years ago
- Comments:19 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@mspae FR created : https://github.com/katspaugh/wavesurfer.js/issues/1237 !
Yes, I agree: In cases where this is useful (when you have peaks) you also know the length in advance and can provide wavesurfer with it.
I meant this commit as a reference how this could work (although this only works for the web audio backend currently) → https://github.com/katspaugh/wavesurfer.js/pull/1210/commits/1025d7263e32f087a3404012dbf0301e5f95b383