Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.8.2
Issue ID
SPLB-369
Regression
No
Spline “Key” Field in Inspector window doesn’t have character limit, breaking Inspector UI
Steps to reproduce:
1. Create new Unity project using Universal 3D Template
2. Open Package Manager window
3. Find and Install “Splines” package
4. Once installed right-click in Hierarchy window > Splines > and create Square
5. In Inspector > Spline Container expand “Int Data”
6. Press “+” to add data to the list
7. In Element 0 > Key add a longer text (for example: NewNameNewNameNewNameNewNameNewNameNewNameNewNameNewName)
8. Observe the Inspector window
Actual results: “Key” field doesn’t have character limit, allowing to add long text breaks Inspector UI
Expected results: “Key” field has character limit, longer text is truncated and doesn’t break Inspector UI
Reproducible with versions: 2.8.2 (6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1)
Tested on (OS): Windows 11, macOS Silicon, Tahoe 26.0 (M1)
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:
Thank you for reporting this issue and helping us identify potential areas for improvement. After careful evaluation, we have determined that this bug has a low impact on functionality or user experience and does not currently align with our immediate priorities. We are unable to address this issue at this time as we are focusing our efforts on higher-priority bugs and improvements that affect core functionality. Thank you for your understanding.