You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix bug, where loop queue is enabled and next() would throw error that there are no more song if current song is last, if loop is enabled the next song after "last" should be "first" again
fixed the return value "willPlayNext" if the "loopQueue" mode is enabled, if the queue is supposed to loop this means that the last song in the queue should have a "willPlayNext" value set to true and not false, as the next song after the last one in the queue will be the first song in the queue
added two new methods, one to change the value of "loopQueue" (setLoopQueue) after player initialization and the second one is a getter (getLoopQueue) method to get the current value of "loopQueue"
finally added some documentation to the players readme
for smoother progress updates the player now internally uses the requestAnimationFrame instead of setInterval to trigger the callback that returns the current songs playing progress
fixed documentation, SOUND_MODE is now PLAYER_MODE and the two currently implemented methods are AUDIO and AJAX and not AUDIO and FETCH as mentioned in v3.0.0
replaced the boolean isPlaying which was the info if the sound is playing or not by a more complex sound state which can be "playing", "stopped" or "paused" to better distinguish between not playing because paused or not playing because stopped