Weird behaviour in login box with apple on-screen keyboard

[DecayingEagle]

Type

Other

Bug description

This is kinda two bugs in one just because they might be very correlated and one is an bug and the other one maybe just an oversight. I am sorry if this will be a bad bug report as this is my first one ever and I know that the title is non-descriptive but this was the best I was able to do at 1am.

Device:
iPad Pro 6th gen 12,9' Cellular 128GB 8GB RAM with a M2 chip running on iPadOS 16.5.1

There are two issues that i have noticed while logging into Osu! on my iPad.

Issue no.1:

Steps to reproduce:

1. Tap on login section of the top UI to open the login box
2. Type in your username by taping on the username field
3. Tap on the password field (do not press enter after typing in username this only happens when you specifically tap on the password field after in) and start typing

When logging in the username and password field is kinda shared. You can see that in the video above the on-screen keyboard the "word prediction" has the username and password after I tried to login with those steps.

Issue no.2:

This is the oversight I was talking about earlier. I've never made an iOS app before but this is something I am pretty sure that is a feature. The password field should have the keyboard for passwords or at least word prediction turned off depending on Apple's implementation of that feature. Currently if you are using a keyboard layout such as English it will show your password while typing it there which I would guess is a small security oversight.

As I said I am new to bug reporting so if you need any more info or anything at all I am more than happy to help.

Screenshots or videos

Untitled.video.-.Made.with.Clipchamp.mp4

Version

2023.621.0 lazer on iPad sideloaded via .ipa

Logs

input.log
network.log
performance.log
runtime.log
database.log

[Susko3]

Since we're using SDL2 for text input on iOS, I've reported issue no.2 to upstream. Since issue no.1 seems to be only visual, and the text appearing is only because of issue no.2 , it doesn't need fixing / consideration.