It would be a nice feature to have, having a button that would appear if the option was selected or had any value, being able to skip from a certain time to another, like when its a recap or the intro of a episode, or even for the next episode at a certain time.

Something like the netflix player or the amazon prime.

for the settings would be like this:

var demo = new Moovie({
    selector: "#example",
    dimensions: {
         width: "100%"
    },
    config: {
        ...
    },
    skip: [
        {
            begin: 20, //seconds
            end: 60 //seconds
        },
        {
            begin: 2400, //seconds
            link: "source.of/next.video.mp4" //seconds
        },
    ]

If you mute the audio, then scrub to a new location of the video, this unmutes the audio. This seems unintuitive to me. I believe the audio should stay muted while scrubbing until the user unmutes it.

When seeking a new position on the progress bar, the loading does not appear, or any type of information.

And when using another type of media, like with the webtorrent example, the progress bar should be fulfilling the parts that are available, or at least, follow the current time ball.

Hello,

I found this while checking out the demo. When i mute the demo and then unmute, sometimes the sound does not come back until i adjust the volume even though the volume is all the way up.

Mac Catalina 10.15.7 Google Chrome Version 89.0.4389.114 (Official Build) (x86_64)

1. Open demo in a fresh incognito browser session
2. Play demo
3. Skip forward
4. Click mute sound button
5. Click unmute sound button
6. Note that sound is no longer muted, and volume is still all the way up. But there is no sound.

I don't have a tool on my mac to show you the actual sound feedback so you can also observe the loss of sound. The issue is consistent in fresh browser session.

Great project! This PR cleans up some of the spacings and syntax differences found throughout the main file with the intention of making this awesome project more maintainable.

Another option might be to look into using something StandardJS to prevent any bike-shedding among devs.

I have implemented a service for a "filesystem over websocket", which is a service that accepts calls in the form of JSON messages. So you have functions like "exists", "read", "write" etc etc all implemented as JSON RPC over websocket. The "real" filesystem just being the users home folder -- so that i can access that from https/ws remotely.

Would it be possible to use your video player to handle data from websocket?

For example, if i could have an event like this in my websocket client:

on["data"] = function (tagId, streamId, bytes) { mooviePlayer.buffer.push (bytes); }

Basically, pushing data into a buffer that the movieplayer is streaming from, then that would make moovie.js by par the most versatile and cool movie player out there.

Hope you think about this, im not the only one having to use WSS for data transport

We could be able to costumize the captions, like, text-border, color, position

When the controls are showing, the subtitles should update the position to be seen every time.

Even when in fullscreen, the subtitles size, are bigger then it should. maybe calculate with a smaller ratio?

I'm building a video streaming site for Operas (2-3 hours long). I had never considered that the <video> element was not suitable for this. Moovie.js calls itself a "Movie focused HTML5 Player". What does that mean, and what's wrong with the HTML5 <video> element?

Thanks for putting it together - looking really neat, with lots of features too. But if you don't figure out specs shortly you may end up fixing what has been fixed over and over again. And the more features are to be introduced, the more likely everything is to start falling apart... believe me I've been there.

Brief

Fixes the new autoplay restrictions where Play() can fail due to Chrome/Safari not registering a user interaction before the video plays (with sound).

Summary

Suppose a video is in an html, which will call video.play to auto-start the video. This video.html is embedded as a same-host iframe. If the user has been using the app then no problem the video autoplays fine.

HOWEVER

If this user takes this link and sends it to one of their friends the video autoplay will fail. In this scenario, chrome/firefox/safaria etc will actually block the video play because the user hasn't click anything yet. The clue that this has happened is that the browser invoke an exception to the promise of video.play(). However, moovie doesn't handle this because the promise is not returned to the caller.

The solution is to change togglePlay() such that the promise is returned to the caller, where the error condition can be gracefully handled.

This enables an attempt at autoplay, with a fallback behavior such as displaying the play.svg button to cue the user to play click the play button. Infact this is exactly the solution I'm using.

I found the new version tag is 1.1.6. it's turn scrubTime change from const into let. But the npm package is not updated,still 1.1.5. This caused my program to fail. Please upadate this