Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.17f1
2023.2.6f1
2023.3.0b3
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
7000.0.0a1
Issue ID
UUM-60756
Regression
No
[TextMeshPro]Input Field becomes uneditable when holding down the LMB, inputting a Japanese character between two other characters, and moving the cursor out of the Input Field
How to reproduce:
1. Open the attached “JapanLetters.zip“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Enter Play Mode
4. Switch to the Japanese IME
5. Put the mouse cursor between the two characters "AA" in the Input Field
6. Press the left mouse button, then press the LMB again and keep holding down the LMB
7. Type any Japanese character
8. While still holding down the LMB, move the cursor out of the Input Field
Expected result: No errors in the Console and the Input Field continues to work properly
Actual result: “ArgumentOutOfRangeException“ error in the Console and the Input Field can no longer be edited
Reproducible with: 3.2.0-pre.6, 3.2.0-pre.7 (2021.3.34f1, 2022.3.17f1), 2023.2.6f1, 2023.3.0b3 (TMPro merged into uGUI)
Couldn’t test with: 4.0.0-pre.1, 4.0.0-pre.2 (2021.3.34f1, 2022.3.17f1) (Errors in the Console)
Reproducible on: macOS 14.0 Sonoma (Intel)
Not reproducible on: No other environment tested
Note: Also reproducible in Player
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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.