Problem/Motivation
I am a happy user of Plyr but found this here on GitHub: https://github.com/sampotts/plyr/discussions/2871
It turns out that there is a new Video.js 10 which includes major improvements. While is still alpha we should see what is needed to get in support for the latest version of Video.js
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork videojs-3577815
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
semiaddict commentedHi,
I need this fairly urgently.
I will thus work on an implementation for Video.js 10 in a fork and will submit an MR soon.
Comment #4
yannickooThe Video.js team has updated their website and now you can already see the beta on https://videojs.org 😏
Comment #5
semiaddict commentedYes. I saw that :)
I submitted a feature request to include dist files as GitHub release assets to be able to use them as library files in the drupal module.
I will use the CDN files for now.
Comment #6
yannickooIs this code from their website not enough?
Comment #7
semiaddict commentedI just pushed a first commit to the 4.x branch that uses the CDN files.
The commit also adds support for audio files.
Comment #8
yannickooThank you for your work @semiaddict, really nice base to continue working on the v10 implementation 💪
Since we cannot have a MR for your changes I need to comment here :D
Could you always add the
playsinlineattribute so mobile browsers can play media inline?Another question re
slot="media"– Why is that needed? The default example on Video.js website says this which does not need aslotattribute:Comment #10
anybodyWhy not create a Draft MR against 3.x and switch over to 4.x once it was created? I did that.
So we can better review and comment the code.
Comment #12
anybody@yannickoo I think we should push things forward here. You've done a great job, would you maybe like to try contacting the current maintainers about their VideoJS 10 and 4.x plans and maybe offer (Co-)maintainership?
We as DROWL team would also like to help if the maintainers are not planning to push this forward. I'd like not to do a fork for that, but didn't see maintainer activity here yet.
@semiaddict I guess you're also interested?
Comment #13
anybodyJust worte @_shy a message asking for further plans:
Comment #14
anybodyI'd vote to have the branch in sync with videojs branch, so let's use 10.x
Comment #15
grevil commentedComment #16
_shyHi guys, thanks for your contribution.
I created a new 4.x branch so we can work with that now. Moved the MR from the Draft state.
Comment #17
anybodyHi @_shy, thanks! Would you accept to use a 10.x branch instead to keep it in sync with the library version this module is based on, for the future?
For library-focused / based modules that makes a lot of sense, because it makes it a lot easier to understand and maintain to keep things in sync. So if VideoJS 11 contains braking changes (due to SemVer) we can simply solve this in 11.x etc.
A really helpful pattern.
Maybe you can still delete 4.x then and make 10.x the default in GitLab?
Comment #18
_shyHi @anybody!
Yes, I agree it makes sense for me. Let's use 10.x branch instead.
Comment #19
_shyComment #20
anybodyThank you so much @_shy! @grevil will start working here right now!
Comment #22
grevil commentedYes already on it. Created a seperate branch and used the work from @yannickoo and @semiaddict as a base.
Comment #23
anybodyComment #25
anybodyComment #26
anybodyReviewing the current status, thanks @grevil!!
Comment #27
anybodyNice work @grevil - left my comments! :)
As discussed we should maybe move the dialog parts into the dedicated follow-up. At least the XHTML part, which doesn't look complete anyway.
Comment #28
grevil commentedAll green! I think this is ready to merge @anybody?
The rest of the features / follow-ups will be done in the other issues
Comment #29
anybodyThanks @grevil great work! Let's merge this and keep 10.x releases in an alpha state for quite a while!
Let's proceed in the follow-ups.
Comment #30
anybody@anyone reading this: Please help us testing and provide feedback!
Comment #33
grevil commentedWe shouldn't release anything for now until the remote formatter and poster works correctly.