Search Issue Tracker
By Design
Votes
0
Found in
6000.0.58f1
6000.2.8f1
6000.3.0b5
6000.4.0a2
6000.5.0a1
Issue ID
UUM-122119
Regression
No
UxmlNamespacePrefix does not apply when using UIBuilder documents
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open UI Builder (Window > UI Toolkit > UI Builder)
3. Click Project in the Library window of UI Builder
4. Add the element: "Custom Controls/MyElements/MyElement" into the Hierarchy
5. Save the UXML file
6. Open the UXML file in a text editor
7. Observe
Expected result: "MyElement" tag is “<elements:MyElement />” and custom xmlns are present
Actual result: There is no custom xmlns set, and the "MyElement" tag is “<MyElements.Runtime.MyElement />”
Reproducible with: 6000.0.58f1, 6000.2.8f1, 6000.3.0b5, 6000.4.0a2
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Reproduction was done by following the steps in this documentation: https://docs.unity3d.com/6000.2/Documentation/Manual/UIE-define-a-namespace-prefix.html
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
Resolution Note:
This is by design. UxmlNamespacePrefix is only used when generating the schema. We may want to support namespaces in the future, but we probably don't want to do it through the attribute; we would want more control on a per-document basis.