Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
2
Found in
2020.3.46f1
2021.3.21f1
2022.2.11f1
2023.1.0b8
2023.2.0a6
2023.3.0a3
6000.0.0b11
Issue ID
UUM-31213
Regression
No
[WebGL] TMPro input field does not prompt a keyboard when in fullscreen mode on a mobile browser
How to reproduce:
1. Open the attached “IN-33305“ project
2. In the File → Build Settings check Development Build and click Build
3. Open the Build directory in a Terminal/Command Prompt and run “python3 -m http.server 8000”
4. Using a mobile device open a browser and type in <yourMachineIP>:8000
5. Click on the Menu (three dots) and check “Desktop View”
6. When the splash screen appears, click on the fullscreen button
7. After the scene loads press on the text input field
Expected result: The keyboard is prompted.
Actual result: The keyboard is not prompted.
Reproducible with: 2020.3.46f1, 2021.3.21f1 - (Reproducible without fullscreen), 2022.2.11f1, 2023.1.0b8, 2023.2.0a6
Built with: macOS 13.2 (Intel)
Reproducible on devices:
VLNQA00334 - Xiaomi Mi A3 (Mi A3), CPU: Snapdragon 665 SM6125, GPU: Adreno 610, OS: 11 (Microsoft Edge, Chrome)
VLNQA00277 - Asus ROG Phone (ASUS_Z01QD), CPU: Snapdragon 845 SDM845, GPU: Adreno 630, OS: 8.1.0 (Firefox, Chrome)
VLNQA00134 - Samsung Galaxy S8 (SM-G950F), CPU: Exynos 9 Octa 8895, GPU: Mali-G71, OS: 9.0.0 (Brave Browser, Chrome)
Not reproducible on devices:
iPhone XR, OS: 16.3.1 (Safari)
Note: TMPro package version used in testing - 3.2.0-pre.4.
Comments (5)
-
ZealousAppex
Oct 05, 2024 01:57
This seems like an important thing to fix and wouldn't take long. There has got to be a large number of people looking for this functionality. Image working on a project for a few years to find out a simple thing like this isn't supported.
-
MSFX
Oct 20, 2023 17:09
2022.3.9f1 with TMP 3.0.6 using a TMP input field I get no keyboard on iOS devices in Chrome
-
Potter76
Oct 01, 2023 23:02
Sorry, I posted twice I was having trouble posting it.
-
Potter76
Oct 01, 2023 23:00
I am using Unity version 2022.3.10f1 with Text Mesh Pro version 3.0.6 and in addition to the mobile keyboard not appearing when I click an input field in my WebGL project in full screen mode on mobile the keyboard does not appear when the game is loaded without clicking the full screen button as well.
-
Potter76
Oct 01, 2023 22:58
I am using Unity version 2022.3.10f1 with Text Mesh Pro version 3.0.6 and in addition to the mobile keyboard not appearing when I click an input field in my WebGL project in full screen mode on mobile the keyboard does not appear when the game is loaded without clicking the full screen button as well.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.0.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.