Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2020.1.0b14
2020.2
Issue ID
1266056
Regression
No
[uGUI] Input Field text can only be submitted using "enter" button
Reproduction steps:
1. Create a new project
2. Create an Input Field
3. Enter Play Mode, select the Input Field and enter some text
4. Press Enter on keyboard
5. Notice how the Caret disappears and text is submitted (the Input Field is de-selected)
6. Exit Play Mode and go Edit -> Project Settings -> Input manager
7. Unbind "Submit" buttons (2 of them or the one that uses "enter" key)
8. Repeat steps 3 and 4
Expected result: the text will not be entered/submitted because the submit button is not binded or it will be possible to bind other buttons to "Submit" button
Actual result: the text is submitted indicating that Input Field text submission cannot be binded to other buttons (Check Notes below)
Reproducible with: 2018.4.26f1, 2019.4.7f1, 2020.1.1f1, 2020.2.0a20
Notes:
1. It is not possible to enter text into Input Field using a controller for example, or any other key for that matter
2. Also reproducible with Input System package
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
- Physics Used Memory keeps growing when GameObject colliders are enabled and disabled
- Errors are thrown and Inspector's UI element is not drawing when a GameObject with script component using a List<T> attached is selected
- ConfigurableJoint's parameters are not saved in the Prefab after Runtime Prefab baking
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
Resolution Note:
if we were to listen for the OnSubmit event (either internally capturing Input.GetButtonDown("Submit"), or by changing the EventSystem to send the OnSubmit first) we hit a issue that enter/return are default submit input axis (and should be) but sending these events to disable the inputfield would prevent entering a new line for multiline input fields. There is no good way to differentiate these scenarios.Derive from InputField and override the function if you want different functionality.