Search Issue Tracker
Fixed
Fixed in 6000.3.4f1, 6000.4.0b4, 6000.5.0a5
Won't Fix in 6000.0.X
Votes
0
Found in
6000.0.62f1
6000.2.13f1
6000.3.0f1
6000.4.0a5
6000.5.0a2
Issue ID
UUM-128920
Regression
No
Template is opened in Isolation when opening it in Context and users Save the UI Document when prompted to do so in UI Builder
Steps to reproduce:
- Open any Project
- Create and open a UI Document Asset
- In the Hierarchy add any Element, right click it and select "Create Template"
- Add any additional Element to the Hierarchy
- In the Stylesheets panel add or create any USS Stylesheet
- Right click the Element that's converted to a Template and select "Open Instance in Context"
- When prompted to Save the file, do so
- Observe the Hierarchy and Stylesheets section
Actual results: When a Template is opened in Context and users save their changes when prompted the Template is opened in Isolation instead
Expected results: Template is opened in Context
Reproducible with versions: 6000.0.62f1, 6000.2.13f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a2
Tested on (OS): Windows 11
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
- Camera.allCameras returns cameras from all loaded Scenes when using multi-Scene setup
- Camera.layerCullDistances has no effect when GPU Resident Drawer is enabled
- ARM64 and ARMv7 APKs return the same version code when "Split APKs by target architecture" is enabled
- Crash on ProfilerMutexLock when closing a project with specific Assets
- “Callback unregistration failed. Callback not registered.” is thrown when changing layouts with two "Font Asset Creator" windows docked
Resolution Note (fix version 6000.5.0a5):
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.4.0b4):
Fixed in 6000.4.0b4
Resolution Note (fix version 6000.3.4f1):
Fixed in 6000.3.4f1
Resolution Note (6000.0.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.