Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Hotkeys prevent you from writing comments on YouTube

  • 2 antwoorden
  • 1 heeft dit probleem
  • 18 weergaven
  • Laatste antwoord van Paul

more options

Hotkeys on YouTube work even when the video window is out of focus, which makes it difficult to write comments. Each press of «f» expands/minimizes the video window, even if the focus is currently on the comment input form.

The bug appeared in one session. No extensions were installed. The latest browser version.

Other browsers are fine.

What could be the problem?

Hotkeys on YouTube work even when the video window is out of focus, which makes it difficult to write comments. Each press of '''«f»''' expands/minimizes the video window, even if the focus is currently on the comment input form. The bug appeared in one session. No extensions were installed. The latest browser version. Other browsers are fine. What could be the problem?

Alle antwoorden (2)

more options

There have been quite a few reports about this YouTube issue recently.

Looks like a YouTube bug where JavaScript always interprets a space bar and other characters as control keys and doesn't disable this action when an input field has focus.

See also:


A possible workaround for now is to write text or affected characters elsewhere (e.g. in the location bar) and paste the clipboard content in the search bar or comment field.

more options

Hi

Thank you for flagging up this issue.

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