
Resolved issue sending beacons when view is ended
#Html5 video player code update#
Update to use navigationStart for timing referenceįix issue where views after videochange might incorrectly accumulate rebuffering duration
#Html5 video player code code#
The error message and code are combined together and aggregated with all errors that occur in your environment in order to find the most common errors that occur. For instance, if your library has two different conditions for network errors, both should have the same player_error_code but different messages.

In general you should not send a distinct code for each possible error message, but rather group similar errors under the same code. However, for custom errors, you should choose a number greater than or equal to 100. If the errors match up with the HTML Media Element Error, you can use the same codes as the corresponding HTML errors. The player_error_code must be an integer, and should provide a category of the error. The player_error_message should provide a generalized description of the error as it happened. When triggering an error event, it is important to provide values for player_error_code and player_error_message. now ( ) // Initialize Mux Data monitoring by passing in the "id" attribute of your video player Import mux from 'mux-embed' const playerInitTime = mux.
