I'm not the only one who hates it: https://www.centbrowser.com/forum/showth...9#pid13449
Not only are the animations ridiculous, since you're adding CPU intensive tasks on top of play/seeking a video, which is already resource intensive, but the player itself is fugly IMO. Could you improve some of these defects, or at least provide deeper hooks for the custom.css feature, so we can affect the shadow DOM and fix it ourselves? The latter would actually be preferable to me.
Edit: Alright, I went back to inspect the new player, and it's not quite as bad as when they first introduced it. I have avoided it like the plague ever since, but they seem to have removed the stupid animations from the timeline/progress bar, so that's a huge improvement. That loading/buffering animation is still the worst though. Not only is it using unnecessary CPU, but it seems to randomly get stuck, so it remains visible even as the video is playing.
Why would anybody want a buffing animation on top of a video that's playing fine? The loading pseudo element has an ::-internal prefix, so it's off limits to user styling like you can with ::-webkit. If you could provide any type of way of getting rid of the loading/buffering animation, the player wouldn't be half bad. God, I hope you can, because that would seriously drive me up the wall every time it gets stuck.
Not only are the animations ridiculous, since you're adding CPU intensive tasks on top of play/seeking a video, which is already resource intensive, but the player itself is fugly IMO. Could you improve some of these defects, or at least provide deeper hooks for the custom.css feature, so we can affect the shadow DOM and fix it ourselves? The latter would actually be preferable to me.
Edit: Alright, I went back to inspect the new player, and it's not quite as bad as when they first introduced it. I have avoided it like the plague ever since, but they seem to have removed the stupid animations from the timeline/progress bar, so that's a huge improvement. That loading/buffering animation is still the worst though. Not only is it using unnecessary CPU, but it seems to randomly get stuck, so it remains visible even as the video is playing.
Why would anybody want a buffing animation on top of a video that's playing fine? The loading pseudo element has an ::-internal prefix, so it's off limits to user styling like you can with ::-webkit. If you could provide any type of way of getting rid of the loading/buffering animation, the player wouldn't be half bad. God, I hope you can, because that would seriously drive me up the wall every time it gets stuck.