[Firefox Developer Edition][119.0b9 (64-Bit)] Key input messed up to 121.0b9 -- fixed since 122.0b1?

[N3tRunn3r]

[ Firefox Developer Edition 119.0b9 ]

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

[N3tRunn3r]

[ Firefox Developer Edition 120.0b5 ]

Hello everyone,

it seems this issue with confused key input has been fixed with update "120.0b5".

Typing fast immediately upon opening FFDE doesnt output false letters anymore, i will continue to test it and let you notice..

[N3tRunn3r]

[ Firefox Developer Edition 120.0b6 ]

It looks like this mess is back .. this can also really confuse my mind about entering my various passwords .. as mentioned earlier, this doesnt apply to the addressbar only but any keyboard input being done within FFDE, if I instantly begin to write whenever FFDE is started..

It has just happened:

a = o; o = o

x = a; a = a

p = s; s = s

etc...

What are you guys doing? This becomes a really serious "unstable" and unprofessional mess ..

[N3tRunn3r]

[ Firefox Developer Edition 120.0b7 ]

Issue still not fixed.

d = s; s = s

..

[N3tRunn3r]

[ Firefox Developer Edition 120.0b9 ]

Hello again,

Firefox Developer Edition has reached V120.0b9 and still this memory issue persists.

l = y; y = y

. = i; i = i

/ = N; N = N

on next day: t = i; i = i

..depends which key I immediately press at first while FFDE has launched, which then causes this mess.

In meantime I have even exchanged and so upgraded all of my Laptop hardware to latest, besides CPU and GPU, done again a fresh & clean install of my OS.. and only FFDE causes this annoying error since V119.0b9 as far as I am aware of!!

I have used FFDE only, for a couple of years yet, and want to keep using it. This struggle however becomes really annoying, frustrating and time-wasting.. as by this issue my entered passwords are so entered wrong too.

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

[N3tRunn3r]

[ Firefox Developer Edition 121.0b1 (64-Bit) ]

Keys are still messed up upon typing quickly whenever FFDE has started..

NumPad: 6 = 1

[N3tRunn3r]

[ Firefox Developer Edition 121.0b3 (64-Bit) ]

Keys still messed up.

3 = n

after minimizing and maximizing FFDE, 3 = 3 with some delay

i wasnt able to test in 121.0b2

[N3tRunn3r]

[ Firefox Developer Edition 121.0b4 (64-Bit) ]

Keys still messed up.

[N3tRunn3r]

[ Firefox Developer Edition 121.0b5 (64-Bit) ]

Keys still messed up. For current example:

m = z

Dear Devs, I soon become really angry by your ignorance if you are NOT able to fix this memory issue..

[N3tRunn3r]

[ Firefox Developer Edition 121.0b6 (64-Bit) ]

Keys still messed up. For current example:

n = o

on next start: y = r

This makes me insane by entering false passwords and other stuff. This issue will force me to switch to crappy bloated Edge after 2 decades of using Firefox.. if you will not fix this very annoying BS, soon !!

[N3tRunn3r]

121.0b7
l = v

121.0b8
0 = e

121.0b9
l = o; o = o

issue still not fixed !!

no,

[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..