Inspector's Preview Theme Dropdown Menu is not updated when switching Project Runtime Theme in the Project Settings

Unity: UI Toolkit Authoring Framework

Won't Fix

6.5.X

Thank you for reporting a bug to Unity. We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available. Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Steps to reproduce:

Open any Project with more than default UI Authoring Themes (e.g. Installing the AI Toolkit Packages)
In the Project Browser create and a UI Document UXML
Select the Asset so it shows up in the Editor's Inspector
Open the Project Settings for UI Toolkit and at the bottom switch the "Runtime" Theme to any and observe the UI Builder Window and the Editor's Inspector

Actual results: UI Builder set Theme is updated but the Editor's Inspector is not redrawn

Expected results: Editor Inspector's Preview Theme Dropdown Menu options are reset with Project Settings switch

Reproducible with versions: 6000.5.0a6

Can’t test with versions: 6000.0.67f1, 6000.3.8f1, 6000.4.0b8 (No Preview Theme Dropdown menu feature)

Tested on (OS): Windows 11

Inspector's Preview Theme Dropdown Menu is not updated when switching Project Runtime Theme in the Project Settings

Unity: UI Toolkit Authoring Framework

Won't Fix

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Inspector's Preview Theme Dropdown Menu is not updated when switching Project Runtime Theme in the Project Settings

Unity: UI Toolkit Authoring Framework

Statuses

Won't Fix

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?