-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Update shaka-player to 4.16.x #7919
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: development
Are you sure you want to change the base?
Conversation
Adding |
i change the volume with the slider but the color wont adjust Freetube.8Hbapf9cpa.mp4 |
I'll change this PR to jump straight to 4.16.0 then, no point doing two separate PRs right after each other (4.16 will also require more changes than just bumping the version). |
@efb4f5ff-1298-471a-8973-3d47447115dc That issue is caused by touch interactions triggering the mouse |
Not review for this PR but SABR implementation seems broken (renderer process taking 100% CPU) after merging this (no code conflict) and I have no idea why... Update 1: even non SABR request can be stuck Update 2: Also got stuck in 4.5.12, not sure if the cause is the same though Update 3: After using local shaka-player repo to checkout tags (long process), it seems to be shaka-project/shaka-player#8782 causing the issue Update 4: Issue with our custom URL triggering a bug in https://github.com/shaka-project/shaka-player/blob/v4.16.0/lib/util/cmcd_manager.js#L1348, adding a fake host seems to workaround it Update 5: Submitted issue shaka-project/shaka-player#9050 |
Testing SABR with this PR: https://github.com/PikachuEXE/FreeTube/actions/runs/17323879326 |
@efb4f5ff-1298-471a-8973-3d47447115dc That error message is not from us, that's coming from webpack's dev server intercepting errors to show in that popup, in this case it's a warning from Electron that an event handler is too slow and may cause performance problems during the resize but as there is nothing in the console I'm pretty sure it is happening inside shaka-player. (reminder that we need to turn off that webpack dev server overlay, as this is not the first time that it has shown irrelevant errors) The only icon of concern is the theatre mode one, all others are different because shaka-player changed Material Icons to Material Symbols to in 0.16.x. |
:deep(.shaka-tooltips-on > .shaka-tooltip-status:active::after), | ||
:deep(.shaka-tooltips-on > .shaka-tooltip-status:focus-visible::after), | ||
:deep(.shaka-tooltips-on > .shaka-tooltip-status:hover::after), | ||
:deep(.shaka-tooltips-on > .shaka-tooltip:active::after), | ||
:deep(.shaka-tooltips-on > .shaka-tooltip:focus-visible::after), | ||
:deep(.shaka-tooltips-on > .shaka-tooltip:hover::after), | ||
:deep(#shaka-player-ui-time-container), | ||
:deep(#shaka-player-ui-thumbnail-container #shaka-player-ui-thumbnail-time-container #shaka-player-ui-thumbnail-time) { | ||
background-color: rgb(0 0 0 / 90%); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@absidue Would it make sense to include this directly in Shaka's CSS?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I'll open a pull request for it.
Pull Request Type
Related issue
Description
shaka-player 4.15 includes a redesigned player UI, which required a few changes to our custom player components as well as the CSS. As the UI changes increase the spacing between the player buttons, I also thought this was a good momement to address Move player controls to the overflow menu which we have been planning to do for a while now. Additionally I switched our audio track selector over to the new
getAudioTracks()
andselectAudioTrack()
API.shaka-player 4.16 changed from using the Material Icons font in the CSS file to using SVGs created via JavaScript, this does mean that the JavaScript file is larger but we no longer need to download the Material Icons font and patch the CSS file to reference the downloaded version.
Screenshots
Testing
Try playing some videos and test that the various UI components work correctly.
Desktop