Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3
2018.3
2019.1
2019.2
2019.3
2019.3.0a6
Issue ID
1161559
Regression
No
"Frame Selected" through "Edit" menu doesn't work if after pressing it, the mouse pointer is not above the Scene view
Reproduction steps:
1. Create a New Project
2. Select any GameObject
3. Press "Edit" -> "Frame Selected" in a way that after pressing the button, the pointer lands on the Scene view
4. Notice that "Frame Selected" focuses the GO
5. Press "Edit" -> "Frame Selected" in a way that after pressing the button, the pointer doesn't land on the Scene view
6. Notice that "Frame Selected" doesn't focus the GO (Might select it in the Hierarchy)
Expected Result: "Edit" -> "Frame Selected" should work in a static way, not dependent one where your pointer lands after the click
Actual Result: "Edit" -> "Frame Selected" works like "F"
Reproduced with: 2019.3.0a6, 2019.2.0b6, 2019.1.7f1, 2018.4.3f1, 2018.3.14f1, 2017.4.29f1
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
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2019.3.X):
low priority defect and unlikely to be fix.