1867859 - [Firefox Developer Edition][119.0b9 (64-Bit)] Key input messed up to "121.0b6"

Status: RESOLVED WORKSFORME

(Core :: DOM: Editor, defect)

Description

[n3trunn3r]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:121.0) Gecko/20100101 Firefox/121.0

Steps to reproduce:

https://connect.mozilla.org/t5/discussions/firefox-developer-edition-119-0b9-64-bit-key-input-messed-up-to/td-p/42279

Greetings,

since a latest version of Firefox Developer Edition [119.0b9 (64-Bit)], if FFDE is started and I quickly type inside the address bar to enter a site upon launching, keys are switched/messed up and outputs false letters.

For example, if I hit the "s-key" it outputs the "c-letter". And many more confused keys. It does also happen in text fields, not just inside the address bar.

Closing FFDE and re-opening does fix it temporarily.

Microsoft Windows 11 Pro, Version 10.0.22631 Build 22631

EDIT:

My latest system specs are now as follows:

Windows 11 Pro 23H2 fresh install + latest stable drivers of all kind
i5-8300H
GTX 1050 Mobile
2x Crucial RAM 16GB DDR4 3200 MHz CL22
Crucial P5 Plus 1TB PCIe 4.0 3D NAND NVMe M.2 Gaming SSD
Crucial MX500 1TB 3D NAND SATA 2,5 SSD

This is a very annoying memory issue and/or bug which corrupts my mind and so creates false input for passwords and anythign else!!

This issue has been existed for about 2 months already..!!!

Best Regards,
N3

Actual results:

For example, if I hit the "s-key" it outputs the "c-letter". And many more confused keys. It does also happen in text fields, not just inside the address bar.

a = o; o = o
x = a; a = a
p = s; s = s
d = s; s = s
l = y; y = y
. = i; i = i
/ = N; N = N
on next day: t = i; i = i
NumPad: 6 = 1
3 = n, after minimizing and maximizing FFDE, 3 = 3 with some delay
m = z
n = o
y = r

...

Expected results:

if i enter s as example, it should output s !!

Comment 1

[:Gijs (he/him)]

Doesn't look like this was intentionally filed as a security issue, so clearing that flag.

If this was happening to everybody we would have long since realized, so something odd must be happening for it to have gone undetected for 2 months. The easiest way to narrow down what broke would be for you to run mozregression to narrow down exactly what change in Firefox broke this on your machine. Is this something you could do? There are instructions available on how to do this. We'd want to know the Pushlog: ... url that it spits out when you finish bisecting.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Address Bar' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 3

[n3trunn3r]

(In reply to :Gijs (he/him) from comment #1)

Doesn't look like this was intentionally filed as a security issue, so clearing that flag.

If this was happening to everybody we would have long since realized, so something odd must be happening for it to have gone undetected for 2 months. The easiest way to narrow down what broke would be for you to run mozregression to narrow down exactly what change in Firefox broke this on your machine. Is this something you could do? There are instructions available on how to do this. We'd want to know the Pushlog: ... url that it spits out when you finish bisecting.

Greetings Gijs,

thank you for your quick response and tag fix.

Sadly I need to say I had done 2 complete fresh & clean Win11 formations/installs since v119.x, when this issue has appeared. So I dont think 'mozregression' will be helpful here. I have even replaced all of my hardware since v119.x, except CPU and GPU on my laptop.

There are sometimes even multiple FFDE updates appearing a day, but this issue still persists. It is pretty annoying as any output within FFDE is false until minimized/maximized or restarted.

It doesnt only appear for the Addressbar in FFDE, but in any input. Entering false *-passwords which makes me insane, etc..

Regards,
N3

Comment 4

[:Gijs (he/him)]

(In reply to n3trunn3r from comment #3)

(In reply to :Gijs (he/him) from comment #1)

Doesn't look like this was intentionally filed as a security issue, so clearing that flag.

If this was happening to everybody we would have long since realized, so something odd must be happening for it to have gone undetected for 2 months. The easiest way to narrow down what broke would be for you to run mozregression to narrow down exactly what change in Firefox broke this on your machine. Is this something you could do? There are instructions available on how to do this. We'd want to know the Pushlog: ... url that it spits out when you finish bisecting.

Greetings Gijs,

thank you for your quick response and tag fix.

Sadly I need to say I had done 2 complete fresh & clean Win11 formations/installs since v119.x, when this issue has appeared. So I dont think 'mozregression' will be helpful here. I have even replaced all of my hardware since v119.x, except CPU and GPU on my laptop.

mozregression is meant to figure out which version of Firefox caused an issue. If there was a version of Firefox that behaved correctly, mozregression should work to figure out what broke - it won't require new hardware or new software. So, just to be clear, you expect that the issue is older than Firefox 119, you just didn't see it on your old hardware / install, for whatever reason?

Comment 5

[n3trunn3r]

121.0b7
l = v

121.0b8
0 = e

121.0b9
l = o; o = o

issue still not fixed !!

Comment 6

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

The point which we want to know is which change caused this bug. Therefore, Gijs requested you to use mozregression to make bisecting the regression range. Could you test this with mozregression? It does not take so long if this is a recent regression.

Comment 7

[Negritas Sergiu, Desktop QA]

Hello! I have tried to reproduce the issue with firefox 122.0a1(2023-12-11) on Ubuntu 22.04 and Windows 10, unfortunately I wasn't able to reproduce the issue on my end. Could you please answer the following questions in order to further investigate this isssue.

1. Does this issue happen with a new profile? Here is a link on how to create one: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
2. Does this issue happen in the latest nightly? Here is a link from where you can download it: https://www.mozilla.org/en-US/firefox/channel/desktop/
3. Do you have any addons installed? If yes could you please list them?

Comment 8

[n3trunn3r]

(In reply to Masayuki Nakano [:masayuki] (he/him)(JST, +0900) from comment #6)

The point which we want to know is which change caused this bug. Therefore, Gijs requested you to use mozregression to make bisecting the regression range. Could you test this with mozregression? It does not take so long if this is a recent regression.

Hello,

I had already mentioned as I had completely formatted my machine for 2 times since this isse has appeared since Firefox Developer Edition v119.0b9.

All data is lost long time ago, mozregression wont work!! And additionally, this issue doesnt happen each time i start Firefox Developer Edition. It is hard to re-produce it. And as told also already, it "usually" happens whenever I type before Firefox Developer Edition is fully loaded up.

Comment 9

[n3trunn3r]

(In reply to Negritas Sergiu, Desktop QA from comment #7)

Hello! I have tried to reproduce the issue with firefox 122.0a1(2023-12-11) on Ubuntu 22.04 and Windows 10, unfortunately I wasn't able to reproduce the issue on my end. Could you please answer the following questions in order to further investigate this isssue.

1. Does this issue happen with a new profile? Here is a link on how to create one: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
2. Does this issue happen in the latest nightly? Here is a link from where you can download it: https://www.mozilla.org/en-US/firefox/channel/desktop/
3. Do you have any addons installed? If yes could you please list them?

Greetings Negritas Sergiu, Desktop QA.

1. It does even happen after a complete fresh installation of Windows 11, as I have told for a few times already. I dont save profiles, but as I had also mentioned, i change security and privacy settings for the installed Firefox Developer Edition. No cookies, Standard Browser Pricavy, Do NOT track setting etc, always use private mode, all permisisons blocked as autorun audio and video and any requests as cam, mic, location, VR, ..., DNS over HTTPS (Cloudflare, maximum settings)..

2. As mentioned a few times already.. I do use Firefox "Developer Edition", current build 121.0b9 (64-bit), and this issue has started to begin with build 119.0b9 (64-bit).. I do not use nightly builds, nor have I setup to receive nightly builds. If this issue also appears on the regular Firefox or on any nightly builds, I do not know it as Firefox Developer Edition is the only browser I do use and have used for many years..

3. The only plugin I do use for Fire Developer Edition is "uBlock Origin". Lately there does also exist an ESET Browser Privacy & Securiy plugin which I test, the ESET plugin has been used way after FFDE v119.0b9.

Comment 10

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

(In reply to n3trunn3r from comment #8)

(In reply to Masayuki Nakano [:masayuki] (he/him)(JST, +0900) from comment #6)

The point which we want to know is which change caused this bug. Therefore, Gijs requested you to use mozregression to make bisecting the regression range. Could you test this with mozregression? It does not take so long if this is a recent regression.

Hello,

I had already mentioned as I had completely formatted my machine for 2 times since this isse has appeared since Firefox Developer Edition v119.0b9.

All data is lost long time ago, mozregression wont work!! And additionally, this issue doesnt happen each time i start Firefox Developer Edition. It is hard to re-produce it. And as told also already, it "usually" happens whenever I type before Firefox Developer Edition is fully loaded up.

You said

So I dont think 'mozregression' will be helpful here

and you haven't clearly said whether you can or cannot reproduce this bug with the old versions too in you new environment. If you reproduce this bug even old versions, your environment has been changed when you update Firefox to 119.0b9.

How frequently do you reproduce this bug? You said

I quickly type inside the address bar to enter a site upon launching, keys are switched/messed up and outputs false letters.

When Firefox receives a native key down message, Firefox scans following char messages in the queue, this should work because when Windows applications receive it, they need to call TranslateMessage API and that puts the char messages into the queue immediately and there is no race with next key down message as far as I know. However, this kind of issues could occur if another application hooks messages for Firefox or just you use odd keyboard layout of 3rd party vendor. Now, my new additional questions are:

• Do you run some applications which filters native events in system wide level? Only ESET?
• Do you reproduce this bug even if you disable (or uninstall) ESET?
• What keyboard layout do you use?

Comment 11

[n3trunn3r]

(In reply to Masayuki Nakano [:masayuki] (he/him)(JST, +0900) from comment #10)
However, this kind of issues could occur if another application hooks messages for Firefox or just you use odd keyboard layout of 3rd party vendor. Now, my new additional questions are:

• Do you run some applications which filters native events in system wide level? Only ESET?
• Do you reproduce this bug even if you disable (or uninstall) ESET?
• What keyboard layout do you use?

It only happens "in" Firefox Developer Edition, and at least "since its release 119.0b9" in October 2023 !!
Any other input and output is correctly system-wide..

As mentioned, this issue doesnt simply appear within the address bar but inside any text field IN forefox Developer Edition. A quick close and relaunch of FFDE temporarily fixes it. Until a next major launch..

Only ESET, I run a minimal system.. I surely wont uninstall ESET when using a Browser .. out of principle.

DE (german) keyboard layout

Today Firefox Developer Edition has got a new release version "122.0b1" (64-bit). This is my 2nd run on this release and this issue hasnt appeared so far yet. I will continue to test it.. whenever I launch FFDE. FFDE uses its special "auroa"-channel, just in case.

Comment 12

[n3trunn3r]

Hello altogether,

it looks like this issue has been finally fixed since Firefox Developer Edition version "122.0b1" and also hasnt re-appeared in version 122.0b2!

I will re-post, if something unusual happens towards this issue again..

Best Regards,
N3

Comment 13

[n3trunn3r]

Attachment: ..issue fixed since FFDE v122.0b1 ?

Comment 14

[Andreas Farre [:farre]]

I'll close this bug, thank you for your investigations. If it does re-appear, feel free to re-open this bug.