Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Can't type in youtube comments without triggering youtube shortcut keys.

  • 3 odgovora
  • 1 ima ovaj problem
  • 3 prikaza
  • Posljednji odgovor od Paul

more options

Like I said in the subject title, I can't seem to type in the comments section of youtube without activating the shortcut key, ie: pressing the spacebar while typing plays/pauses the video, and the space does not appear, f toggles the fullscreen, m toggles mute, and other shortcut keys in youtube.

I have tried firefox safe mode (add-ons disabled), and the same thing happens. This only occured today, and nothing was wrong yesterday.

Commenting in youtube on other browsers, edge, chrome, and opera seems to be working properly.

I'm using Firefox 86.0 64bit.

Like I said in the subject title, I can't seem to type in the comments section of youtube without activating the shortcut key, ie: pressing the spacebar while typing plays/pauses the video, and the space does not appear, f toggles the fullscreen, m toggles mute, and other shortcut keys in youtube. I have tried firefox safe mode (add-ons disabled), and the same thing happens. This only occured today, and nothing was wrong yesterday. Commenting in youtube on other browsers, edge, chrome, and opera seems to be working properly. I'm using Firefox 86.0 64bit.

Izabrano rješenje

YouTube have looked into this and will be correcting the issue very shortly.

Pročitaj ovaj odgovor u kontekstu 👍 1

Svi odgovori (3)

more options

Hi

Thank you for flagging up this issue.

YouTube have looked into this and will be correcting the issue shortly.

more options

Update: Apparently, so is the search bar, even when there is no video playing or in youtube home page, I can't type anything properly. Other sites are working fine, just youtube.com.

more options

Odabrano rješenje

YouTube have looked into this and will be correcting the issue very shortly.