Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Hotkeys prevent you from writing comments on YouTube

  • 2 replies
  • 1 has this problem
  • 18 views
  • Last reply by Paul

discipler6
discipler6
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?

All Replies (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
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.

Paul
Paul
  • Top 25 Contributor
  • Moderator
more options

Hi

Thank you for flagging up this issue.

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