Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2021.2.0a16
2021.2.0b5
2022.1
Issue ID
1354329
Regression
No
[macOS] DisplayInfo.workArea is incorrect after scaling any display while having app in fullscreen mode
Steps to reproduce:
1. Open the attached project ("1354329.zip")
2. Open "SampleScene"
3. Build and run for standalone (press Esc once in build to see the settings panel)
4. Go to System Preferences -> Displays
5. Fullscreen the app
6. Switch to Display settings
7. Choose any custom scaling for any display from Display -> Resolution
8. Switch back to the app and observe the workArea data
Expected results: DisplayInfo.workArea stays the same size
Actual results: DisplayInfo.workArea is reported as maximum, no longer ignoring menu bar or dock sections
Reproducible on: 2021.2.0a16, 2021.2.0b5, 2022.1.0a4
Couldn't test with versions older versions as MoveWindowAPI was introduced in 2021.2.016
Notes:
- Not reproducible with different scaling on Windows
- Once reproduced, to return to the previous state need to go back to windowed mode on the app and change screen scaling again (doesn't matter if to a custom or default one)
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a11. workArea is updated accordingly to any scaling changes or FullScreenMode changes
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b15