Copyright © 2026 Unity Technologies
2023.1 is no longer a supported version of Unity. Please see the corresponding 2023.2 port instead (if applicable).
Thank you for bringing this issue to our attention. After careful consideration, we will be closing the 2022.3.X port as this issue will be resolved in a newer release. This decision is determined by factors such as severity, frequency of the issue, and the number of users affected by it. For more details, please refer to the latest port related to this issue. We apologize for any inconvenience this may cause and appreciate your understanding.
Thank you for bringing this issue to our attention. After careful consideration, we will be closing the 2021.3.X port as this issue will be resolved in a newer release. This decision is determined by factors such as severity, frequency of the issue, and the number of users affected by it. For more details, please refer to the latest port related to this issue. We apologize for any inconvenience this may cause and appreciate your understanding.
Reproduction steps:
1. Open the attached “Test Project” project
2. Open “Scripts/UI/Resources/UXML1” Asset
3. Add ‘xmlns:uic=”UI.Controls”’ namespace in line 1
4. Add “<uic:CustomControl />” Element below line 5
5. Open Window > UI Toolkit > UI Builder window
6. Select “Assets/Scripts/UI/Resources/UXML1.uxml” file the “Library” tab
7. Move any element in the “Hierarchy” tab and save the changes
8. Open “Scripts/UI/Resources/UXML1” Asset
9. Observe the Element’s (added in step 4) tag
Expected result: The tag stays the same “uic:CustomControl”
Actual result: The tag changes to “UI.Controls.CustomControl”
Reproducible with: 2023.2.0a17
Couldn’t test with: 2021.3.26f1, 2022.3.0f1, 2023.1.0b19 - No support for “UxmlAttributeAttribute” and “UxmlElementAttribute”
Reproducible on: Windows 10
Issues you vote on will appear here