Search Issue Tracker
Fixed in 1.0.0-preview.19
Fixed in 1.0.0-preview.18
Votes
0
Found in [Package]
0.11.0-preview
Issue ID
1363722
Regression
Yes
UI Builder applies previously loaded USS to a new UXML
Reproduction steps:
1. Open the attached "case-1363722-2022.zip" project
2. Open the UI Builder window
3. Add the "Button" Control from the Library
4. In the Viewport enable Preview
5. Hover over the Button inside the Viewport and observe the color change
6. Save and close this UXML
7. Open MyUXML.uxml (Assets > MyUXML)
8. Reopen the previously created UXML
9. Repeat steps 4-5
Expected result: The Button does not turn green because "MyUSS" StyleSheets has not been added to this UXML
Actual result: The Button turns green as if it had the "MyUSS" StyleSheet added
Reproducible with: 0.11.0-preview (2019.4.30f1, 2020.3.18f1, 2021.1.21f1), 1.0.0-preview.17 (2019.4.30f1, 2020.3.18f1, 2021.1.21f1), 2021.2.0b12, 2022.1.0a9
Not reproducible with: 0.10.2-preview (2019.4.30f1, 2020.3.18f1, 2021.1.21f1)
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (fix version 1.0.0-preview.19):
Fixed in 1.0.0-preview.19 (2022.1.0a13)
Resolution Note (fix version 1.0.0-preview.18):
Fixed in 1.0.0-preview.18
Resolution Note (fix version 1.0.0-preview.18):
Fixed in 1.0.0-preview.18 (2021.2.4f1)