Re: Broken arrow keys for browser access to proxmox and ESXi

More information.

- Disabling wayland in gtk3 and rebuilding all packages does not
resolve the issue
- librewolf works - the output from https://keyjs.dev/ is below

firefox/firefox140/firefox128/palemoon: (bad keymapping)

e.key      e.code       e.which e.keyCode
ArrowLeft  Convert      37      37
ArrowUp                 38      38
ArrowRight NonConvert   39      39
ArrowDown  NumpadEnter  40      40

chromium: (bad keymapping)

e.key      e.code       e.which e.keyCode
ArrowLeft  Convert      37      37
ArrowUp    Lang3        38      38
ArrowRight NonConvert   39      39
ArrowDown  NumpadEnter  40      40

chromium: (bad keymapping)

e.key      e.code       e.which e.keyCode
ArrowLeft  Convert      37      37
ArrowUp    Unidentified 38      38
ArrowRight NonConvert   39      39
ArrowDown  NumpadEnter  40      40

librewolf: (works!)

e.key      e.code       e.which e.keyCode
ArrowLeft  ArrowLeft    37      37
ArrowUp    ArrowUp      38      38
ArrowRight ArrowRight   39      39
ArrowDown  ArrowDown    40      40

arcticfox: (segv on start)

badwolf/netsurf: (cannot run test)

dillo: ctype(3) abuse crash on attempting to load page

otter-browser: ERR_CERT_AUTHORITY_INVALID on attempting to load any page



On Fri, 2 Jan 2026 at 10:25, RVP <[email protected]> wrote:
>
> On Fri, 2 Jan 2026, Martin Husemann wrote:
>
> >> Could this be it? If I try the arrow keys here:
> >>
> >> https://keyjs.dev/
> >>
> >> `e.code' isn't what corresponds to the physical layout--it shows what you said.
> >
> > Very interesting - it also happens in Palemoon.
> >
>
> GTK issue? As a first step, I'd try disabling wayland:
>
> https://github.com/NetBSD/pkgsrc/blob/trunk/x11/gtk3/options.mk#L13
>
> so that bringing that and `libxkbcommon' in doesn't confound things. (I'm
> travelling at the mo', so don't have mucho compute cycles to do this.)
>
> -RVP