Search Issue Tracker
Fixed
Fixed in 2021.3.54f1, 2022.3.65f1, 6000.0.54f1, 6000.1.12f1, 6000.2.0b10, 6000.3.0a2
Votes
0
Found in
2021.3.53f1
2022.3.64f1
6000.0.52f1
6000.1.9f1
6000.2.0b8
6000.3.0a1
Issue ID
UUM-110450
Regression
Yes
EditorGUILayout.Toggle clickable area is shifted when using Built-in Render Pipeline
How to reproduce:
1. Open the attached “IN-105703” project
2. In the toolbar, navigate to Edit > Preferences…
3. Select the “Bug UI” tab
4. Click on the checkbox of “Foo” or “Bar” properties
5. Observe the clicked checkbox
Expected result: The checkbox is toggled on/off when clicked
Actual result: The checkbox is not toggled on/off when clicked
Reproducible with: 2021.3.53f1, 2022.3.64f1, 6000.0.0b11 (a707ca4efec4), 6000.0.52f1, 6000.1.9f1, 6000.2.0b8, 6000.3.0a1
Not reproducible with: 2023.3.0b10
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Checkboxes are highlighted when hovering over with a mouse cursor
- Checkboxes can be toggled when clicking between the checkbox and the property name
- Does not reproduce when “Universal RP” package is installed
Comments (1)
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
airaolagoitia
Nov 28, 2025 16:32
Starting in 2022.3.65f1, we see the same issue "checkbox is not toggled on/off when clicked". It seems the click zone doesn't match the rendered UI. I guess this fix broke some other thing?
The issue we see is not in 2022.3.64.