Clicking next too quickly causes player control lockup

[cclark-00]

Issue description

Clicking 'next song' button too rapidly causes JS error getFloat in bufferedProgressElements.js parseFloat call due to config.buffered being NaN.

Environment

Windows 10 home

• What's My Browser Support link: Firefox 75

• Amplitude.js Version: 5.0.3

Steps to reproduce the issue

1. Click next song rapidly. Not reliably reproducible. Could be due to a large (90+) playlist, or using Amplitude.init callbacks; it only started showing up after those two additions to my JS code.

What is expected?

Link to where issue can be reproduced

Additional details / screenshots

Sample fix is in my fork. I tested config.buffered for NaN before running getFloat in 3 places.

[danpastori]

I added the changes from your fork. Thanks for pointing that out! It's a good check to have in there before trying to compute a failing number.