Unable to type spaces and other characters (f, m) into YouTube search bar
Categories
(Web Compatibility :: Site Reports, defect)
Tracking
(firefox-esr78 fixed, firefox86 fixed, firefox87 fixed, firefox88 fixed)
People
(Reporter: standard8, Unassigned)
References
Details
Various users are reporting that we they are unable to type in spaces into the search bar on youtube.
I have reproduced this on both Firefox Release (86.0) and the latest nightly build on Mac. It fails with tracking protection off as well.
There are no error messages on the web console.
|
Reporter | |
Comment 1•4 years ago
|
||
This also appears to affect Safari.
Opera and Google Chrome work fine.
|
||
Comment 6•4 years ago
|
||
If you're on a video, F and M also triggers the UI (fullscreen, mute, and space triggers play/stop).
|
||
Comment 8•4 years ago
|
||
All Firefox versions are affected.
| Comment hidden (me-too) |
|
||
Comment 10•4 years ago
|
||
Quoting an email I just sent to our contacts,
There's a
keydownhandler on theyt-hotkey-manager, which also gets triggered every time something is typed into the search bar. This event eventually ends up in https://www.youtube.com/s/desktop/01a10dcc/jsbin/desktop_polymer_inlined_html_polymer_flags.vflset/desktop_polymer_inlined_html_polymer_flags.js, in a function calledonKeyDownEvent_.The noticable difference here is that when typing into the search bar in Firefox,
this.ignoreKeyEvent_(a)returnsfalse, while in Chrome, this istrue. Looking into this function is a bit tricky, as it's hard to read without having the sources, buta.pathjumped out.ais the KeyboardEvent, andpathis an attribute that should not be there. It looks like Chrome is supplying ... soemthing here (looks like the event's bubbling path maybe?), but this attribute is non-standard and I don't even really know what it does. It's undefined in Firefox and Safari.Looks like relying on this attribute is breaking things here.
|
|
||
Comment 12•4 years ago
|
||
It's possible that this is meant to be Shadow DOMs bubbling path, but in that case, this code should be a.composedPath(), which would work in all modern browsers. Chrome appears to be supporting path only for legacy reasons, see https://bugs.chromium.org/p/chromium/issues/detail?id=740870 and potentially other issues.
|
||
Comment 13•4 years ago
•
|
||
(presumably comment 9 did not mean to reset the affected flags, so I'm re-setting them)
| Comment hidden (off-topic) |
| Comment hidden (off-topic) |
|
||
Comment 16•4 years ago
|
||
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.
| Comment hidden (off-topic) |
|
|
||
Comment 18•4 years ago
|
||
It seems to be working correctly for me now.
|
|
||
Comment 19•4 years ago
|
||
Yes, confirmed as fixed by the YouTube team.
|
||
Comment 20•4 years ago
|
||
Confirmo que Youtube fue solucionado en Firefox x64 y Nigthy
|
||
Comment 21•4 years ago
|
||
It's working now. Thanks everyone!
|
||
Comment 22•4 years ago
|
||
|
|
||
Updated•4 years ago
|
|
|
||
Updated•4 years ago
|
|
||
Comment 24•4 years ago
|
||
Actually, not fixed.
For brevity (people with ergonomic needs still exist) let's say you have custom shortcuts like b to toggle bookmarks toolbar.
On google.com or any other page except youtube, b will toggle your thing as long as you are not focusing an input field.
Once you focus an input field, control is passed to the webpage and it's typing literal b or whatever the page wants.
On youtube.com on the other hand, all input fields are broken (search, comment) and pressing b will toggle your thing instead of typing b !
Funny thing is that it's case-sensitive and you can still type capital B.
This bug report should be reopened until youtube fully reverts whatever they broke.
|
|
||
Comment 25•4 years ago
|
||
No longer an issue even in the context above, 78esr/86/88
Description
•