Search Issue Tracker
Won't Fix
Won't Fix in 2022.3.X, 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
2022.3.54f1
6000.0.31f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-91184
Regression
No
TMP Input Field becomes not interactable when pasting a long text
Reproduction steps:
1. Open the attached “Unity 6 UI bug.zip” project
2. Open the “SampleScene TMP” Scene
3. Copy a large amount of text (Can be paragraphs from here:[https://www.lipsum.com/])
4. Enter the Play mode
5. Paste the text into the Input Field
6. Click anywhere on the Input Field a few times
7. Try to type something in the Input Field
Expected result: Input Field is interactable and text is entered
Actual result: Nothing happens, the text is not interactable
Reproducible with: 2021.3.47f1, 2022.3.54f1, 6000.0.31f1, 6000.1.0a7
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- Does not happen with Legacy text
- The issue is most present when the resolution in the Game view is set to “Free Aspect”, “16:9” or “16:10”
- Also reproduces in the 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
- VFX Graph Documentation dropdown button does nothing when clicked on the right side
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
Resolution Note:
This issue occurs when disabling the Image component on the root of a multi-line InputField, and inserting just enough text to cause the Text object (content) to be pushed up and outside of the Text Area object (viewport). Normally, the Image on the root of the InputField ensures that there is a raycastable graphic available to receive input across the entire visible area of the InputField. Disabling this Image component means that only the Text object can receive raycasts. The Text object is also not resized based on content by default, so its size will not grow with the size of the text content and can end up being moved entirely outside of the effective viewport.
Thus, this issue can be worked around in several ways:
1. Add an enabled Image component with an alpha value of 0 to the Text Area object to ensure the effective viewport can detect raycasts.
2. Reenable the Image component on the root of the InputField and set its alpha to 0 to ensure the entire InputField can detect raycasts.
3. Add a Content Size Fitter to the Text object, with "Vertical Fit" set to "Preferred Size" to ensure the Text object always overlaps with the effective viewport.
Resolution Note (6000.4.X):
This issue occurs when disabling the Image component on the root of a multi-line InputField, and inserting just enough text to cause the Text object (content) to be pushed up and outside of the Text Area object (viewport). Normally, the Image on the root of the InputField ensures that there is a raycastable graphic available to receive input across the entire visible area of the InputField. Disabling this Image component means that only the Text object can receive raycasts. The Text object is also not resized based on content by default, so its size will not grow with the size of the text content and can end up being moved entirely outside of the effective viewport.
Thus, this issue can be worked around in several ways:
1. Add an enabled Image component with an alpha value of 0 to the Text Area object to ensure the effective viewport can detect raycasts.
2. Reenable the Image component on the root of the InputField and set its alpha to 0 to ensure the entire InputField can detect raycasts.
3. Add a Content Size Fitter to the Text object, with "Vertical Fit" set to "Preferred Size" to ensure the Text object always overlaps with the effective viewport.
Resolution Note (6000.3.X):
This issue occurs when disabling the Image component on the root of a multi-line InputField, and inserting just enough text to cause the Text object (content) to be pushed up and outside of the Text Area object (viewport). Normally, the Image on the root of the InputField ensures that there is a raycastable graphic available to receive input across the entire visible area of the InputField. Disabling this Image component means that only the Text object can receive raycasts. The Text object is also not resized based on content by default, so its size will not grow with the size of the text content and can end up being moved entirely outside of the effective viewport.
Thus, this issue can be worked around in several ways:
1. Add an enabled Image component with an alpha value of 0 to the Text Area object to ensure the effective viewport can detect raycasts.
2. Reenable the Image component on the root of the InputField and set its alpha to 0 to ensure the entire InputField can detect raycasts.
3. Add a Content Size Fitter to the Text object, with "Vertical Fit" set to "Preferred Size" to ensure the Text object always overlaps with the effective viewport.
Resolution Note (6000.2.X):
This issue occurs when disabling the Image component on the root of a multi-line InputField, and inserting just enough text to cause the Text object (content) to be pushed up and outside of the Text Area object (viewport). Normally, the Image on the root of the InputField ensures that there is a raycastable graphic available to receive input across the entire visible area of the InputField. Disabling this Image component means that only the Text object can receive raycasts. The Text object is also not resized based on content by default, so its size will not grow with the size of the text content and can end up being moved entirely outside of the effective viewport.
Thus, this issue can be worked around in several ways:
1. Add an enabled Image component with an alpha value of 0 to the Text Area object to ensure the effective viewport can detect raycasts.
2. Reenable the Image component on the root of the InputField and set its alpha to 0 to ensure the entire InputField can detect raycasts.
3. Add a Content Size Fitter to the Text object, with "Vertical Fit" set to "Preferred Size" to ensure the Text object always overlaps with the effective viewport.
Resolution Note (6000.0.X):
This issue occurs when disabling the Image component on the root of a multi-line InputField, and inserting just enough text to cause the Text object (content) to be pushed up and outside of the Text Area object (viewport). Normally, the Image on the root of the InputField ensures that there is a raycastable graphic available to receive input across the entire visible area of the InputField. Disabling this Image component means that only the Text object can receive raycasts. The Text object is also not resized based on content by default, so its size will not grow with the size of the text content and can end up being moved entirely outside of the effective viewport.
Thus, this issue can be worked around in several ways:
1. Add an enabled Image component with an alpha value of 0 to the Text Area object to ensure the effective viewport can detect raycasts.
2. Reenable the Image component on the root of the InputField and set its alpha to 0 to ensure the entire InputField can detect raycasts.
3. Add a Content Size Fitter to the Text object, with "Vertical Fit" set to "Preferred Size" to ensure the Text object always overlaps with the effective viewport.
Resolution Note (2022.3.X):
This issue occurs when disabling the Image component on the root of a multi-line InputField, and inserting just enough text to cause the Text object (content) to be pushed up and outside of the Text Area object (viewport). Normally, the Image on the root of the InputField ensures that there is a raycastable graphic available to receive input across the entire visible area of the InputField. Disabling this Image component means that only the Text object can receive raycasts. The Text object is also not resized based on content by default, so its size will not grow with the size of the text content and can end up being moved entirely outside of the effective viewport.
Thus, this issue can be worked around in several ways:
1. Add an enabled Image component with an alpha value of 0 to the Text Area object to ensure the effective viewport can detect raycasts.
2. Reenable the Image component on the root of the InputField and set its alpha to 0 to ensure the entire InputField can detect raycasts.
3. Add a Content Size Fitter to the Text object, with "Vertical Fit" set to "Preferred Size" to ensure the Text object always overlaps with the effective viewport.
Resolution Note:
This issue occurs when disabling the Image component on the root of a multi-line InputField, and inserting just enough text to cause the Text object (content) to be pushed up and outside of the Text Area object (viewport). Normally, the Image on the root of the InputField ensures that there is a raycastable graphic available to receive input across the entire visible area of the InputField. Disabling this Image component means that only the Text object can receive raycasts. The Text object is also not resized based on content by default, so its size will not grow with the size of the text content and can end up being moved entirely outside of the effective viewport.
Thus, this issue can be worked around in several ways:
1. Add an enabled Image component with an alpha value of 0 to the Text Area object to ensure the effective viewport can detect raycasts.
2. Reenable the Image component on the root of the InputField and set its alpha to 0 to ensure the entire InputField can detect raycasts.
3. Add a Content Size Fitter to the Text object, with "Vertical Fit" set to "Preferred Size" to ensure the Text object always overlaps with the effective viewport.