Search Issue Tracker
By Design
Votes
0
Found in [Package]
3.0.3
Issue ID
1298827
Regression
No
[Mobile] Rich Text is editable when "Allow Rich Text Editing" is disabled
Reproduction steps:
1. Open the attached project “Case956757_TMP”
2. Build and Deploy to a device
3. In the Build, tap on the Input Field in the Scene
4. Make sure that the text in the input field is not highlighted
5. Press backspace to delete the first emoji
6. Press backspace again
Expected result: All the text should be deleted OR the rich text should be displayed as an emoji in the input as well
Actual result: Only the last character of the text gets deleted AND the Rich Text is displayed in the input instead of an emoji
Reproducible with: TMP 1.4.1 (2018.4.30f1), 2.0.1 (2019.4.16f1), 3.0.1 (2020.1.17f1, 2020.2.0f1), 3.0.3 (2021.1.0a10)
Reproduced with:
iPhone 6 (iOS 12.4.8)
iPhone 7 (iOS 12.3.1)
iPhone 12 mini (iOS 14.1)
VLNQA00012, Samsung Galaxy S6 (SM-G920F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
----------, Samsung Galaxy S9 (SM-G960F), Android 10, CPU: NOT FOUND, GPU: Mali-G72
----------, Samsung Galaxy J4 Core (SM-J410F), Android 8.1.0, CPU: Snapdragon 425 MSM8917, GPU: Adreno (TM) 308
VLNQA00321, Xiaomi MI 9 (MI 9), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Could not reproduce with:
Editor on Mac
Player on Mac
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
- UnityLinker causes crash when outputting snapshot data for very large projects
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
Resolution Note:
This behavior is related to the fact, the text is being displayed and edited in the native iOS text field above the soft keyboard which is an implementation that is platform specific and in this case controlled by Apple. As such, none of the rich text tags unique to TMP have any meaning in this native text field. Basically this native text field will always show the RAW text.