,, when the accessibility setting for rising the in game focused chat is enabled (or anything but the vanilla default AFAIK), the links and "click here" prompts do not work. buttons such as the police badge one for chat reporting stuff make a noise on click though display nothing/no change
Expected Behaviour
,, expected behavior: the chat buttons such as the police badge (located on the right) should work as they usually do
Screenshots
No response
Reproduction Steps
,, hit up on the DPad, and click on the police badge on the right. this is all the while the Accessibility setting, "On-screen keyboard height" is anything but the default/vanilla
Logs
No response
Mod Version
newest as of 2/23/24,, can get version # if needed (sorry)
Controller
steam deck
Bluetooth
[ ] Yes
Operating System
Linux/SteamOS
ARM
[ ] Yes
Additional Information
tried keywords to find this issue in issue tracker and found nothing so I am sorry if this has been reported previously
Just to make sure...
[X] I have made sure I am using the latest version of Controlify for the latest version of Minecraft.
[X] I have made sure there are no other issues describing the same problem on the issue tracker.
Current Behaviour
,, when the accessibility setting for rising the in game focused chat is enabled (or anything but the vanilla default AFAIK), the links and "click here" prompts do not work. buttons such as the police badge one for chat reporting stuff make a noise on click though display nothing/no change
Expected Behaviour
,, expected behavior: the chat buttons such as the police badge (located on the right) should work as they usually do
Screenshots
No response
Reproduction Steps
,, hit up on the DPad, and click on the police badge on the right. this is all the while the Accessibility setting, "On-screen keyboard height" is anything but the default/vanilla
Logs
No response
Mod Version
newest as of 2/23/24,, can get version # if needed (sorry)
Controller
steam deck
Bluetooth
Operating System
Linux/SteamOS
ARM
Additional Information
tried keywords to find this issue in issue tracker and found nothing so I am sorry if this has been reported previously
Just to make sure...