VM/container console, colons/semicolons, and Firefox variants?

[steevestroke]

I've looked in the docs and on the forums and cannot find any reference to this issue but it has been consistent for me for several years...

Has anyone else noticed that when entering input into the VM/container Console in the VE web console colons entered via Firefox are not being properly handled and are showing up as semicolons? It appears as though the Shift key is not being recognized. This is very consistent across Firefox variants and Debian-based OSes. On the same machines Brave Browser does not exhibit this behavior.

Any easy work around for this is to enter that input via SPICE client but not every workload I have in Proxmox supports SPICE for console access.

 

[vshab]

Can you e.g. create file and fill it with colons/semicolons, and then open console with other browser to see if this is a visual bug or key codes are different?

 

[steevestroke]

I could but I'm very confident its not a visual bug as I have done other work where I was doing things involving colons and semicolons where I had to pivot over to a SPICE client or Brave Browser to get it to work. Think scripting etc.

 

[vshab]

I think that might be a bug with xterm.js. I suggest filling out a bug report on the xterm.js GitHub page (or searching for it, I did find some related to firefox and ligatures, but IDK); maybe someone there can help figure it out.

 

[steevestroke]

I wonder what other software embeds xterm.js? I would be useful data to see I can repro there as well.

 

[steevestroke]

I think portainer uses xterm.js so I tried a container console and was not able to repro. Admittedly a bit of a loose test.