Search Issue Tracker
Fixed in 1.5.4, 2.1.4, 3.0.4
Votes
0
Found in [Package]
1.5.0-preview.1, 2.1.0
Issue ID
1299798
Regression
Yes
Having a UTF32 character in an Input Field allows rich text editing when "Allow Rich Text Editing" is disabled
Reproduction steps:
1. Open the attached project "Case_1299798" and load "SampleScene"
2. Enter Play Mode
3. Delete the word "Red" from the Input Field using Backspace
4. Press Backspace again
Expected result: Rich Text does not get deleted
Actual result: The last character of the Rich Text gets deleted
Reproducible with: TMP 1.5.0-preview.1, 1.5.3 (2018.4.30f1), 2.1.0, 2.1.3 (2019.4.16f1), 3.0.1, 3.0.3 (2020.1.17f1, 2020.2.0f1, 2021.1.0a10)
Not reproducible with: TMP 1.4.1 (2018.4.30f1), 2.0.1 (2019.4.16f1)
Notes: See "RichTextEditing.mov" for a reproduction video
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 1.5.4, 2.1.4, 3.0.4):
Fixed in TMP 1.5.4, 2.0.4, 3.0.4