Skip to content

Conversation

@AskMP
Copy link
Collaborator

@AskMP AskMP commented Jul 24, 2019

I have updated the class to account for event listeners as well as updated the initial code for it to be driven with imports.

The visualizer has been completely removed from the original player class and is now a stand-alone element that can be replaced with others' ideas.

The ability to update the mount that the player is connecting to is also added however it should be noted that there is no check to confirm it is ONLY fcc URLs that are used. This can technically take any audio filepath and apply it to the audio element. Not much of a security issue but just something to note.

AskMP added 6 commits July 23, 2019 17:23
I've added several event emitters throughout the class in hopes to eventually take all DOM manipulation out of the player class. It should all be within the app level instead and simply use events and variables from the class.
The bitrate should now automatically select the 64kbps if the connection speed is 3G or slower. Users can also choose the speed manually via a select box that will now be generated on desktop.
Unless the browser supports the navigator.connection and the connection speed is above 3G, the gif animation and the cover art is not shown.
Call to action added along with the hiding and showing of the meta data upon playing and pausing.

Also corrected a bug where music was auto starting by default and causing dom exceptions. It now requires an action by the user to start.

Changing the bitrate before a stream does NOT instigate an auto play however changing it after playback has happened results in it remaining its last state continuing.
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