61–65 of 65 posts
It may also mean a light framework on top of Web Components, but getting rid of all these dependencies and ever-changing framework is of course an old dream.
it really whips to llama's ass.
What's left for Web Components to get in order to completely get rid of frameworks like VueJS and React? By getting rid of I mean for 99% of use cases. It may also mean a light framework on top of Web Components, but getting rid of all these dependencies and ever-changing framework is of course an old dream.
For everyone else, you start running into the issue of the classic https://xkcd.com/927/ situation. The problem of ever-changing frameworks will always be a constant. People want different things from their frameworks!
controls=0 – Removes the player controls (like play, pause, volume). modestbranding=1 – Minimizes the YouTube logo in the player. rel=0 – Prevents showing related videos at the end (only works to show videos from the same channel). showinfo=0 – Removes the video title and uploader info (this parameter is deprecated but modestbranding should help). fs=0 – Disables the fullscreen button. iv_load_policy=3 – Hides video annotations (like pop-up notifications).
Then have your code detect for youtube embed urls and use a iframe to create the player (rather than a video tag). Finally map your player controls to the youtube embed api. Plyr.io have done something similar.