Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
4.3.4f1
Issue ID
597323
Regression
No
Unity Editor's concept of "maximized" not correct
Steps to reproduce:
1. Change monitor resolution to smaller than maximum.
2. Open Unity Editor, maximize the window.
3. Close the Editor.
4. Change resolution to higher
5. Open the same project. Editor will not be filling up the screen. Double-clicking on window title for the first time will not cause it to maximize. On tested machine window jumps slightly down and onto another monitor.
6. Later double-clicking on Editor Window title will cause it to toggle maximize properly.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment