Numeric input fields show standard OSK on (initial) focus

[tarek-y-ismail]

Related? #3580

When focusing on numeric input fields, TextInputV?::set_content_type (checked V1 and V3) successfully sets the hint and purpose, yet the OSK that pops up is the standard character/numeric OSK. This occurs with both the iot example (Electron, TextInputV1), and WPE webkit (TextInputV3). This also occurs with the w3 schools HTML example, and Inductive Automation's Ignition demo

Reproduction steps:

1. Get the iot-example or WPE webkit, and ubuntu-frame-osk
2. Launch one of the URLs mentioned above

• To change the URL for the iot example: Open snap/snapcraft.yaml, replace the url inside loadURL
• To change the URL for WPE webket: sudo snap set wpe-webkit-mir-kiosk url=<url>

3. Launch miral-app, the iot example, and ubuntu-frame-osk:

• WAYLAND_DISPLAY=wayland-99 ./path/to/miral-app --add-wayland-extensions=all
• WAYLAND_DISPLAY=... iot-example-graphical-example
• WAYLAND_DISPLAY=... ubuntu-frame-osk

4. Click on the number field

Expected: A numerical keyboard pops up
Reality: The standard keyboard pops up

[Saviq]

Is the content type forwarded to the OSK on the input method protocol?

We really need to get maliit working so we can have a comparison…

[tarek-y-ismail]

Is the content type forwarded to the OSK on the input method protocol?

Yep. I set a breakpoint in TextInputV1::set_content_type and it sure is set, but I didn't follow it around.

We really need to get maliit working so we can have a comparison…

I think I got that working yesterday under GNOME. It just launches now

[Saviq]

Yep. I set a breakpoint in TextInputV1::set_content_type and it sure is set, but I didn't follow it around.

That's the client side, it's the input-method-unstable-v2 protocol that Mir then communicates with the OSK software - and forwards client requests to. If the content type hint gets lost in Mir, we've to fix that. But if it correctly gets forwarded to the OSK, the issue is there.

As we know, it does at least work sometimes with the numerical input fields, so there is a question about where does it get lost when it doesn't work.