Pressing the same key multiple times produces different characters as if typing across the same row of keyboard keys from left to right.
Categories
(Core :: Widget: Win32, defect)
Tracking
()
People
(Reporter: stephen_moran, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0
Steps to reproduce:
This started after updating to the latest FireFox 116.0.1 (64-bit) update over the last few days on my desktop (64-bit win10 Pro) and a laptop (64-bit Win10 Home), both configured quite differently from each other.
Now press the same (or any) keyboard key once or multiple times anywhere, including the address bar, eMail, or anything.
Actual results:
This then displays different (wrong) characters as if typing across the same row of keyboard keys from left to right, then down to the next row once reaching the end.
For instance: qwertyuiop[]\asdf etc.
Gives the same output regardless of which key is pressed, or how many times the same key is pressed. All other applications other than Firefox work correctly.
Expected results:
FireFox should display keyboard input as entered.
This is not just a display issue, as FireFox is actually interpreting the keyboard input incorrectly. This is confirmed when my typed security password is rejected, but a cut&past of the same password is accepted and works.
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Password Manager' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•2 years ago
|
||
The severity field is not set for this bug.
:serg, could you have a look please?
For more information, please visit BugBot documentation.
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Lets try the Widget win32 component as a place to start looking into this.
Comment 4•2 years ago
|
||
@gstoll, does this sound that third-party anti-keylogger kernel-module issue you mentioned? Do we have an existing bug for it?
Yes. I'm new here, but believe this bug was triggered by interaction with the Zone Alarm Anti-Keylogger and resolved in Bug 1847033 with Firefox version 116.0.2, at least that's been my experience and all appears to be working well for me with Zone Alarm anti-keylogger re-enabled.
Comment 6•2 years ago
|
||
Yes, that is correct - thanks! (and apologies for the issue)
Description
•