Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Keys not working properly on YouTube

  • 2 Antworten
  • 1 hat dieses Problem
  • 15 Aufrufe
  • Letzte Antwort von Paul

more options

Hey folks! When I try to type in the YouTube search bar during a video, the keys I type perform some actions on the current video instead of just typing in the search bar. For example when I type f in the YouTube search bar it changes current video to fullscreen, when I type t, it changes to cinema mode. Spacebar just pauses/unpauses the video instead of putting space.

This problem just occured today, before that everything was working fine. Also everything works perfectly on other browsers. The problem only occurs in Firefox.

Hey folks! When I try to type in the YouTube search bar during a video, the keys I type perform some actions on the current video instead of just typing in the search bar. For example when I type '''f''' in the YouTube search bar it changes current video to fullscreen, when I type '''t''', it changes to cinema mode. '''Spacebar''' just pauses/unpauses the video instead of putting space. This problem just occured today, before that everything was working fine. Also everything works perfectly on other browsers. The problem only occurs in Firefox.

Alle Antworten (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.