Search Issue Tracker
Not Reproducible
Votes
2
Found in
6000.0.42f1
6000.1.0b11
6000.2.0a7
6000.3.0a1
Issue ID
UUM-100241
Regression
Yes
[IME][Windows]The most recently entered character is ignored in the OnSubmit event when entering text using IME in a TMP_InputField
Reproduction steps:
1. Install the Korean language pack
2. Open the attached “BugRepro” project
3. Open the “Assets/Scenes/StartScene.unity“ Scene
4. Enter the Play Mode
5. In the Game view, enter the Korean character "아" (D and K keys) in the Input Field manually
6. Press the Enter key
7. Observe the Console window
Expected result: "아" message is displayed
Actual result: The empty message is displayed
Reproducible with: 3.2.0-pre.5 (2023.2.0a13), (Built-in) 2023.2.0a14, 6000.0.42f1, 6000.1.0b11, 6000.2.0a7
Not reproducible with: 3.2.0-pre.4 (2023.2.0a13)
Couldn't test with: 4.0.0-pre.1 (2023.2.0a13) error CS0029: Cannot implicitly convert type 'uint[]' to 'int[]', 4.0.0-pre.2 (2023.2.0a13) warnings Font Asset was not found
Reproducible on: Windows 11
Not reproducible on: Does not reproduce on MacOS
Notes:
- This issue does not occur when enabling “Previous version of Microsoft IME” under Microsoft IME compatibility mode
- Not reproducible when using copy & paste
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Cannot reproduce. We did a great number of changes to IME and InputFields in general, one of them fixed it. It will be fixed in the next package release of TMP for 2022.3-