Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

4K Youtube video froze at 16 minutes and 10 seconds in after 136.0 update

  • Nie ma odpowiedzi
  • 0 osób ma ten problem
more options

Hello, I just updated Firefox to version 136 on my MacBook Pro. I was playing a 4k YouTube video, and at 16 minutes and 10 seconds in the video froze. If I moved the cursor the pause button and all of that would come up at the bottom, but when I clicked on the option to exit full screen it did not respond. I pressed the escape button and that did get me out of full screen, but the video window did not apply the right formatting. I'll include a screenshot so that you can see what I am talking about. After exiting full screen, if you look at the bottom of the video window, the option to go back to full screen is cut off. Closing Firefox and relaunching it appears to have things working again, at least for now. I thought it would be best to report this just in case it isn't an isolated glitch.

Hello, I just updated Firefox to version 136 on my MacBook Pro. I was playing a 4k YouTube video, and at 16 minutes and 10 seconds in the video froze. If I moved the cursor the pause button and all of that would come up at the bottom, but when I clicked on the option to exit full screen it did not respond. I pressed the escape button and that did get me out of full screen, but the video window did not apply the right formatting. I'll include a screenshot so that you can see what I am talking about. After exiting full screen, if you look at the bottom of the video window, the option to go back to full screen is cut off. Closing Firefox and relaunching it appears to have things working again, at least for now. I thought it would be best to report this just in case it isn't an isolated glitch.
Załączone zrzuty ekranu

Aby odpowiadać na posty, musisz zalogować się na swoje konto. Zadaj pytanie, jeśli nie masz jeszcze konta.