npx grunt build fails: "Required config property "copy.undefined" missing about web-media-controller HOT 5 CLOSED

Sorry, Gruntfile.js is a mess now. I'll try to fix it.

from web-media-controller.

Thanks. As for the invidio.us support I'd like to contribute, I was wondering whether you could help me a little bit getting inside the code. I have a question:

I'm trying to understand the way a connector works by reading the existing ones. As I see, the most important variables in a connector are the selectors I. If I give a selector (take nextButtonSelector for example) a value of div#continue and the first link inside it will lead to the next video, should it be good enough or should I find a selector that will lead straight to a link that targets the next video?

from web-media-controller.

If I give a selector (take nextButtonSelector for example) a value of div#continue and the first link inside it will lead to the next video, should it be good enough or should I find a selector that will lead straight to a link that targets the next video?

You could see content/base-connector.js to make a better idea of what happens there. In this case, when next signal comes from outside, connector.next() is called. Its implementation in base-connector.js among other things tries to get the first element that matches nextButtonSelector and then tries to call elem.click(). If there is no click()able element, you could just implement next() from scratch in your connector.

from web-media-controller.

I've also fixed Gruntfile.js and corresponding README info.

from web-media-controller.

I've also fixed Gruntfile.js and corresponding README info.

Cool.

You could see content/base-connector.js to make a better idea of what happens there. In this case, when next signal comes from outside, connector.next() is called. Its implementation in base-connector.js among other things tries to get the first element that matches nextButtonSelector and then tries to call elem.click(). If there is no click()able element, you could just implement next() from scratch in your connector.

Wonderfully explained. One more question please regarding the mediaSelector: I tried to set it to just video with the hope that it will eventually make the playPause() functions work just like in YouTube but it didn't work.

However, I've managed to test the addEventListener in the console like so:

document.querySelector('video').addEventListener("pause", function(){ console.log("paused")})

I've also tried to use playButtonSelector without success while I did managed to run this in the console:

document.querySelector('.vjs-play-control').click()

According to your explanation, both of these console tests should simulate what the extension does only with a few wrappers from content/utils.js right?

from web-media-controller.