DataBinding causes the UXML file to be considered as modified when no changes are made

Unity: UI Builder

Won't Fix

2023.2.X

Thank you for bringing this issue to our attention. After careful consideration, we will be closing the 2023.2.X port as this issue is resolved in the LTS version (6000.0.X). 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.

How to reproduce:
1. Open the “BugReport.zip“ project
2. Open the “BugReport02“ scene
3. Open the “MainScreen.uxml“ in the UI Builder window
4. Select the “Vector3Field“ UI element under “VisualElement2“ in the Hierarchy in the UI builder window
5. Close the UI Builder window

Expected results: When no changes are made, the “UI Builder - Unsaved Changes Detected“ Dialog Box does not appear
Actual results: When no changes are made, the “UI Builder - Unsaved Changes Detected“ Dialog Box appears

Reproducible in: 2023.2.14f1, 2023.3.0a4
Not reproducible in: 6000.0.0b11
Could not test in: 2021.3.36f1, 2022.3.21f1 (Console errors which are caused by the missing Data Binding functionality)
Fixed in: 2023.3.0a5

Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested

Note: Only reproducible in the reporter's attached project which uses Data Binding

DataBinding causes the UXML file to be considered as modified when no changes are made

Unity: UI Builder

Won't Fix

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

DataBinding causes the UXML file to be considered as modified when no changes are made

Unity: UI Builder

Statuses

Won't Fix

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?