Search Issue Tracker
Third Party Issue
Votes
0
Found in
6000.4.0a2
Issue ID
UUM-125470
Regression
No
[macOS] Cursor issues when main window is fullscreen and floating window doesn't have focus
Repro steps (macOS only):
- Start Unity with no floating windows open
- Switch to the default layout, with the Project view open
- Press the green button to put Unity into fullscreen mode
- Select Windows->Analysis->Profiler in the menu bar. Note that in this case, the floating window will stay on top of the full-screen main window.
- Change the profiler mode to "Editor" and record a few frames.
- Select a frame from the "highlights" view (topmost row usually)
- Line up the highlights view in the bottom pane so it partialy overlaps the edit box of the main editor's project window
- Select the main window and click in the search box of the projects window. Now slowly move the mouse cursor to the left over the highlights view in the unfocused floating window
Actual behavior: Itermittently the cursor will change to the I-beam when it should be an arrow. It looks like macOS is selecting the rect from the cursor under the window. However, if you slowly drag left past when the project view search box has ended, it remains an I-beam.
Expected behavior: The cursor should be an arrow since the project view search box we are over is obscured by the profiler window
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
We've identified the issue as a general bug with AppKit and raised the issue to Apple through their feedback tracker.