搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

YouTube hotkeys issues in FireFox

  • 3 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 Paul

more options

YouTube video player hotkeys react even when video is out of focus. I can't write a comment under the video on YouTube, because when I type, the hotkeys for the video are triggered. I immediately tested this problem on other devices - it's the same there. At the same time, this problem is not observed in other browsers (Chrome).

FireFox v 86.0, Windows 10.

YouTube video player hotkeys react even when video is out of focus. '''I can't write a comment under the video on YouTube''', because when I type, the hotkeys for the video are triggered. I immediately tested this problem on other devices - it's the same there. At the same time, this problem is not observed in other browsers (Chrome). FireFox v 86.0, Windows 10.

所有回复 (3)

more options

Looks like a YouTube bug where JavaScript always interprets a space bar press as play/pause and doesn't disable this action when an input field has focus.

See also:

A possible workaround for now is to place this character on the clipboard (i.e. type a space and select it and copy the space to the clipboard) and paste the clipboard content. You can possibly use the location bar to get the space on the clipboard.

more options

cor-el said

Looks like a YouTube bug where JavaScript always interprets a space bar press as play/pause and doesn't disable this action when an input field has focus. See also: A possible workaround for now is to place this character on the clipboard (i.e. type a space and select it and copy the space to the clipboard) and paste the clipboard content. You can possibly use the location bar to get the space on the clipboard.

Yes, the error is similar. But reacts not only to the spacebar, it reacts to all hotkeys: F, E, M, etc. And only in FireFox. This problem is not observed in other browsers.

more options

Hi

Thank you for flagging up this issue.

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