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!

Овај сајт ће имати ограничену функционалност док га будемо ажурирали у циљу побољшања вашег искуства. Ако неки чланак не реши ваш проблем и желите да поставите питање, на располагању ће вам бити наше заједнице подршке @FirefoxSupport на Twitter-у и /r/firefox на Reddit-у.

Avatar for Username

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

Ова тема је архивирана. Питајте друго питање ако вам је потребна помоћ.

Firefox interference with typing YouTube comments?

  • 6 одговорa
  • 1 има овај проблем
  • 4 прегледа
  • Последњи одговор послао joelchummel

joelchummel
joelchummel
more options

I have always used Firefox with YouTube and often add comments or reply to existing comments.

Today I noticed that when typing a comment, my keystrokes were being intercepted as keyboard shortcuts directed at the video player. I'd type a word, press the space bar, and the video would pause. I confirmed my keystrokes against YouTube's list of video oriented keyboard shortcuts, and sure enough, anything typed while in text-edit mode in the comments section were being redirected to the video player.

This doesn't affect Chrome. After I discovered this in Firefox I tried there.

I made sure my browser cache was cleared, made sure my Firefox was up to date, disabled my adblocker, even rebooted my computer.

Not sure if anyone has seen this issue, just hoping.

I have always used Firefox with YouTube and often add comments or reply to existing comments. Today I noticed that when typing a comment, my keystrokes were being intercepted as keyboard shortcuts directed at the video player. I'd type a word, press the space bar, and the video would pause. I confirmed my keystrokes against YouTube's list of video oriented keyboard shortcuts, and sure enough, anything typed while in text-edit mode in the comments section were being redirected to the video player. This doesn't affect Chrome. After I discovered this in Firefox I tried there. I made sure my browser cache was cleared, made sure my Firefox was up to date, disabled my adblocker, even rebooted my computer. Not sure if anyone has seen this issue, just hoping.

Изабрано решење

https://bugzilla.mozilla.org/show_bug.cgi?id=1697551#c16

The YouTube team has verified the bug on their site and is rolling back the website update. This should be fixed soon for all users.
Прочитајте овај одговор са објашњењем 👍 1

Сви одговори (6)

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.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Одабрано решење

https://bugzilla.mozilla.org/show_bug.cgi?id=1697551#c16

The YouTube team has verified the bug on their site and is rolling back the website update. This should be fixed soon for all users.
joelchummel
joelchummel Власник питања
more options

WOW! I am amazed at the amount of awareness and expertise I find in the Firefox community, thanks to all who responded, and my hat is off to you for being so knowledgeable and caring.

joelchummel
joelchummel Власник питања
more options

Problem solved already! The video player in YouTube is no longer intercepting keystrokes from the comment text-editing mode. Search bar also working again.

Paul
Paul
  • Top 25 Contributor
  • Moderator
more options

Hello,

I am glad to hear that your problem has been resolved. If you haven't already, please select the answer that solves the problem. This will help other users with similar problems find the solution.

Thank you for contacting Mozilla Support.

joelchummel
joelchummel Власник питања
more options

@Seburo,

Dilemma! Can only pick one answer as having solved the problem. I picked the other contributor because the link he included led me to a wider discussion and that was what made me realize not only that many others were already aware of the issue and that it was already being fixed.

But I thank you as well for your concern!