Search Issue Tracker
Fixed in 2021.2.X
Votes
1
Found in
Issue ID
1320914
Regression
No
Loading invalid UXML or USS returns non null object
Loading UXML or USS files with errors returns non-null object. The import shows errors but you can still do
var mysheet = AssetDatabase.LoadAssetAtPath<StyleSheet>("MyBad.uss");
and I get a non null (mysheet != null) StyleSheet object with empty data.
MyBad.uss:
Label {
font-size: 20px;
-unity-font-style: bold;
color: rgb(68, 138, 255); dsdd >
Note: Instantiating the returned VisualTreeAsset
will return a null VisualElement though
Comments (1)
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
- The Inspector rounds up float values up to a maximum of 7 digits and overwrites the actual values in the file when saving the asset
- Distant Shadowmask does not cast Shadows on Terrain when baking with Adaptive Probe Volumes
- UI Toolkit Debugger "Text Overlays" dropdown is opened in the wrong position when Dynamic Atlas Viewer is opened
- NullReferenceExceptions are thrown on Editor launch when the Project window was locked in the previous project
- Render Pipeline Converter selected asset counter reports one fewer item when using manual selection
mattone593
Mar 12, 2021 01:54
LOADING INVALID UXML OR USS RETURNS NON NULL OBJECT
UI Toolkit-Mar 11, 2021
Loading UXML or USS files with errors returns non-null object. The import shows errors but you can still do
var mysheet = AssetDatabase.LoadAssetAtPath<StyleSheet>("MyBad.uss");
and I get a non null (mysheet != null) StyleSheet object with empty data.
MyBad.uss:
Label {
font-size: 20px;
-unity-font-style: bold;
color: rgb(68, 138, 255); dsdd >