[Bug\VB-17656] Fullscreen HTML5 video: Slow and harsh change to/from fullscreen
-
Hi, I find few issues while changing YouTube HTML5 video on to and from fullscreen. With Flash video, there's no problem, and change is flawlses without any resizing of Vivaldi windows. With HTML5 video I've got these issues: [b]Change to fullscreen:[/b] Slow and harsh change to fullscreen. It looks like video is moved in its original size to left top corner while rest of screen is black. Then video is resized to match fullscreen. [b]Change from fullscreen: [/b] Size is resized back to smaller one. But with video also whole Vivaldi windows is resized to small winow. Then after few seconds windows is maximazed again. But this whole process take seconds. So it's really annoying. Please take a look at it. Thank you in advance. Configuration: [spoiler] [table] [tr] [td]Vivaldi - Stable[/td] [td]1.1.453.59 (Stable channel) (64-bit)[/td] [/tr] [tr] [td]Vivaldi - Developer[/td] [td]1.2.479.8 (Developer Build) (64-bit)[/td] [/tr] [tr] [td]OS[/td] [td]Windows 7 x64[/td] [/tr] [/table] [/spoiler] [b]Update[/b]: VB-17656: Fullscreen HTML5 video: Slow and harsh change to/from fullscreen
-
HTML5 means a little.
Likely you are talking about Vp9 videos which are not HW accelerated. Try to use h264ify to get the mp4/h264 version od the same video
-
Hi,
I guess most important is this strange behavior of resizing of video container and Vivaldi windows itself. It should not happend aside from what kind of video format it is in container.
-
I have the same problem!
-
I had another problem with fullscreen (on YouTube): going to fullscreen was ok but reversing went all wrong - I pressed Escape to exit fullscreen but instead of leaving fullscreen the player was just resized to fit the browser window. The whole browser window was visible and everything else was just the player and the video. The only way I could fix this was to engage fullscreen again and then disengage it which actually did fix it.
This doesn't happen every time but it happens quite often and is not too hard to reproduce on v1.3.544.25. -
I still have this problem
-