Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2023.1.0a25
2023.2.0a1
Issue ID
UUM-22841
Regression
Yes
[UITK] Buttons don't get focused when they are custom-made by the user
Reproduction steps:
1. Open the attached project “FocusRepro”
2. Open Window → App UI → StoryBook window
3. In the StoryBook window click on Kit → Main
4. Press the “Tab” button multiple times
Expected result: The focus cycles through all buttons
Actual result: The focus skips custom-made buttons
Reproducible with: 2022.2.0a18, 2023.1.0a1, 2023.1.0a25
Not reproducible with: 2021.3.16f1, 2022.1.24f1, 2022.2.2f1
Couldn’t test with:2020.3.44f1 - This version doesn’t have a built-in UI Toolkit
2022.2.0a1 - 2022.2.0a8 - Third-party package errors
Reproducible on: macOS 13.1 (Intel)
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
This will be fixed with the new UXML Serialization feature in versions 2023.2 and after as they now detect the actual default value instead of relying on the UxmlTraits.
Fix in 2023.2 won't be backported as it's part of a feature work. A workaround is to override the default value of the attribute in the UxmlTraits of the element (see examples like PackageList, SelectableLabel and SearchFieldBase).
Resolution Note (2023.2.X):
This will be fixed with the new UXML Serialization feature in versions 2023.2 and after as they now detect the actual default value instead of relying on the UxmlTraits.
Fix in 2023.2 won't be backported as it's part of a feature work. A workaround is to override the default value of the attribute in the UxmlTraits of the element (see examples like PackageList, SelectableLabel and SearchFieldBase).