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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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 >