[RESOLVED] Firefox input fields

quietcornerlinux · 2023-08-18 13:20:57

I have recently been having an issue with firefox. When I click on a websites input field and start typing, sometimes it works as expected. Other times, one or two letters are entered and then there is the "page down" action when I am mid typing. Focus is taken off the input field. I am using the firefox package from the extra repo. System is up to date. I am using gnome with wayland. I have no issues using epiphany or any other app.

Firefox 116.0.3

* firefox - extra repo
* firefox - flatpak
* all plugins are disabled
* search for text when you start typing is disabled
* refresh firefox
* firefox safe mode
* launched using `$ MOZ_ENABLE_WAYLAND=1 firefox`
* remove firefox-gnome-theme - aur package

Any ideas would be appreciated.

Last edited by quietcornerlinux (2023-09-11 14:52:23)

seth · 2023-08-18 13:45:41

gnome on wayland or xorg?
native wayland firefox or xwayland?
=> https://wiki.archlinux.org/title/Firefox#Wayland

quietcornerlinux · 2023-08-19 11:57:40

seth wrote:

gnome on wayland or xorg?
native wayland firefox or xwayland?
=> https://wiki.archlinux.org/title/Firefox#Wayland

Wayland. I did try `$ MOZ_ENABLE_WAYLAND=1 firefox` and it yielded no resolution. I forgot to mention it. Will edit original post.

quietcornerlinux · 2023-08-19 12:13:07

I tried loading gnome with xorg. Firefox would work with all keys except "s", epiphany would only work with a few keys, and text editor would work with them all. Switch back to wayland, and I can't get anything to mess up. I am more confused than ever.

seth · 2023-08-19 12:15:11

Do you have a spare keyboard?

quietcornerlinux · 2023-08-31 13:09:35

seth wrote:

Do you have a spare keyboard?

Sorry for the late response. I was on vacation, and then had an update go bad (now resolved).

I do not have a spare keyboard. I do not think it is the keyboard. It works perfectly fine in the terminal, text editor, or any other app. It works fine in firefox sometimes, if I reload the page. It's driving me nuts. Any help is appreciated.

Trilby · 2023-08-31 13:19:31

Does this happen on all websites or selectively on some? I've found the modern trend of reinventing simple functional things like <input> tags with highly complex js framework toolkits can result in very oddly behaving input fields on poorly made pages.

quietcornerlinux · 2023-08-31 13:31:35

Trilby wrote:

Does this happen on all websites or selectively on some? I've found the modern trend of reinventing simple functional things like <input> tags with highly complex js framework toolkits can result in very oddly behaving input fields on poorly made pages.

It happens on all websites. It has happened even on this forum. Reloading the page, clicking on the url bar and back, switching apps and back, all solutions to get the keyboard to work properly again.

Last edited by quietcornerlinux (2023-08-31 13:32:34)

seth · 2023-08-31 13:33:12

Firefox would work with all keys except "s", epiphany would only work with a few keys, and text editor would work with them all. Switch back to wayland, and I can't get anything to mess up

Other times, one or two letters are entered and then there is the "page down" action when I am mid typing.

Spurious input, possibly from a touchpad/screen?

Focus is taken off the input field.

where does it go? Page? location bar? Other window?

sudo libinput list-devices

quietcornerlinux · 2023-08-31 13:53:56

seth wrote:

Firefox would work with all keys except "s", epiphany would only work with a few keys, and text editor would work with them all. Switch back to wayland, and I can't get anything to mess up
Other times, one or two letters are entered and then there is the "page down" action when I am mid typing.
Spurious input, possibly from a touchpad/screen?
Focus is taken off the input field.
where does it go? Page? location bar? Other window?
sudo libinput list-devices

I will try to do a video tonight showing and explaining what happens.

Device:           Power Button
Kernel:           /dev/input/event1
Group:            1
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

Device:           Power Button
Kernel:           /dev/input/event0
Group:            2
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

Device:           Creative Technology Ltd Creative Pebble Pro Consumer Control
Kernel:           /dev/input/event19
Group:            3
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

Device:           Creative Technology Ltd Creative Pebble Pro
Kernel:           /dev/input/event20
Group:            3
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

Device:           Primax Kensington Eagle Trackball
Kernel:           /dev/input/event16
Group:            4
Seat:             seat0, default
Capabilities:     pointer 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   button
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   flat *adaptive custom
Rotation:         0.0

Device:           ckb1: CORSAIR K55 RGB PRO Gaming Keyboard vKB
Kernel:           /dev/input/event15
Group:            5
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

Device:           ckb1: CORSAIR K55 RGB PRO Gaming Keyboard vM
Kernel:           /dev/input/event17
Group:            6
Seat:             seat0, default
Capabilities:     pointer 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   button
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   flat *adaptive custom
Rotation:         0.0

seth · 2023-08-31 14:01:54

Try to remove the speakers but my money is now on the g4m0rz keyboard… with an additional pointer device.

quietcornerlinux · 2023-09-11 14:52:07

seth wrote:

Try to remove the speakers but my money is now on the g4m0rz keyboard… with an additional pointer device.

Thank you seth. The only reason I ended up with that keyboard is because my logitech G413 unit failed. I used the BestBuy warranty, but they had no equivalent unit in stock. I hate corsair keyboards.

I purchased a Keychron K4P-G2. Awesome keyboard at reasonable price. Very clicky. No stupid rgb colors. Good form factor. Arrow keys are in weird position.

Switching keyboards did not resolve the problem. However, the problem no longer exists. I am guessing that it was some app that I either updated, or removed. Perhaps ckb-next? I honestly don't know because it was an intermittent issue.

seth · 2023-09-11 15:09:41

Switching keyboards did not resolve the problem. However, the problem no longer exists.

?

I am guessing that it was some app that I either updated, or removed.

No userspace process will generate spurious events in evtest.
That's either a kernel bug or, more likely, the hardware.

quietcornerlinux · 2023-09-11 16:57:34

The issue still persisted after swapping keyboards. Only the past few days has it been without error. You mentioned a kernel bug. Looking back, a kernel update did occur about the same time everything started working correctly.

I'm just glad I can work again and my son can do his school work.

Arch Linux

#1 2023-08-18 13:20:57

[RESOLVED] Firefox input fields

#2 2023-08-18 13:45:41

Re: [RESOLVED] Firefox input fields

#3 2023-08-19 11:57:40

Re: [RESOLVED] Firefox input fields

#4 2023-08-19 12:13:07

Re: [RESOLVED] Firefox input fields

#5 2023-08-19 12:15:11

Re: [RESOLVED] Firefox input fields

#6 2023-08-31 13:09:35

Re: [RESOLVED] Firefox input fields

#7 2023-08-31 13:19:31

Re: [RESOLVED] Firefox input fields

#8 2023-08-31 13:31:35

Re: [RESOLVED] Firefox input fields

#9 2023-08-31 13:33:12

Re: [RESOLVED] Firefox input fields

#10 2023-08-31 13:53:56

Re: [RESOLVED] Firefox input fields

#11 2023-08-31 14:01:54

Re: [RESOLVED] Firefox input fields

#12 2023-09-11 14:52:07

Re: [RESOLVED] Firefox input fields

#13 2023-09-11 15:09:41

Re: [RESOLVED] Firefox input fields

#14 2023-09-11 16:57:34

Re: [RESOLVED] Firefox input fields

Board footer