Skip to content
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

Resizing video frame resizes frames temporarily, then flicks back to a different size. #2357

Closed
jfrux opened this issue Aug 29, 2019 · 3 comments

Comments

@jfrux
Copy link

jfrux commented Aug 29, 2019

What do you want to do with Hls.js?
I want to be able to resize the video after playback has started and keep the image at that size.
This is happening on a vizio tv in a chrome engine version 68+.

Is there a way I can trick it to stay the size I specify? Even if it's like some hackery?
Or even just refresh something on an interval?

What have you tried so far?
I've ensured the video element itself is actually the size I specified and not somehow being hidden by a div or something.

Notice in the GIF above, I select the video that has resized itself inside the video element somehow and I press Enter, which expands it to full screen.

Then I hit Back, which is resizing it back to the small version and the video stays that size temporarily... maybe until the video buffer changes or something?

I do not see anything out of the ordinary when setting "debug: true".

@stale
Copy link

stale bot commented Oct 28, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Oct 28, 2019
@itsjamie
Copy link
Collaborator

itsjamie commented Oct 29, 2019

Did you find a resolution to this issue? For regular Chrome 68, there should be no issue like this where the render surface seems to lag behind. I'm assuming what I should be noticing is the cut-off logo in the top-left (news[y])

@stale
Copy link

stale bot commented Dec 28, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Dec 28, 2019
@stale stale bot closed this as completed Jan 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants