Open TheGreenAirplane opened 5 months ago
Hi @TheGreenAirplane, could you please try the 24/edge
channel of ubuntu-frame-osk
?
It has a much newer version of the OSK software itself (squeekboard).
Hi, thank you for your response. I installed the keyboard via snap: sudo snap install ubuntu-frame-osk
if you could elaborate what exactly is this 24/edge channel, I'll be sure to give it a try.
Ok so I asked ChatGpt what is a "24/edge channel" and with its help I was able to install ubuntu-frame-osk from the 24/edge channel. My changes to the layout are still being ignored, but at least now the keyboard is 3 times smaller than it should be. So it's definitely progress, just not in the right direction :)
Yeah, the being smaller is why we've not updated to the newer version (#46)… Thanks for confirming.
I could confirm your problem using url=https://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_input_type_number. I suspect it's an upstream issue, will try and confirm and report it there.
Hi, is there any update on this? It's causing us issues in production. Apparently if you ask people to type in a number, and don't give them a purely numeric keyboard, they get confused and type in the letter "o" instead of zero. Has this been escalated to Squeekboard devs? Or should I do it? Did you manage to confirm that the problem is with Squeekboard code and not ubuntu-frame-osk?
@TheGreenAirplane there are three components here that need to work in unison:
It would be great if you could try reproducing the problem replacing these components (e.g., using Sway as the compositor, or building upstream Squeekboard). That could help pinpoint where the problem lies.
I'm not aware of a different keyboard software implementing the same Wayland protocols, but browsing through GitHub might yield one:
https://github.com/search?q=virtual-keyboard-unstable-v1.xml&type=code
Hello, I've been told to inquire about the status of this bug. Has there by any chance been some progress on this?
@TheGreenAirplane it would helpful if you could do some investigation to clarify which component is misbehaving.
I am not an advanced Linux user, I don't have the skill set to perform these tests.
@TheGreenAirplane sorry, it will have to wait until we have some free time on our hands. Because of all the layers ultimately resulting in this issue, it's not at the top of our backlog.
Possibly related to https://github.com/canonical/mir/issues/3580?
I have an input element, , which is supposed to trigger the numpad layout. However, it only shows up if I've had another input already selected. If I select a non-numeric input, the regular keyboard comes up, if I then select the numeric input, I get the numpad.
But if I select the numeric input first, I get the regular keyboard. If I deselect an input, causing the keyboard to hide, and then select a numeric input, I get the regular keyboard again.
The numeric keyboard should show up consistently, every time a numeric input is selected.
I'm running the latest (as of 5 days ago) versions of Ubuntu Server, Ubuntu Frame, Mir Kiosk, and Ubuntu Frame OSK.