Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
0
Found in
2018.3.6f1
Issue ID
1157039
Regression
No
Windows player always on top after switching ExclusiveFullScreen to FullScreenWindow
To reproduce:
1. Open attached project "screenmode.zip"
(Note you may need to start the application in Windowed mode for this to reproduce.)
2. Build and Run on Standalone
3. When in application, press '1' to switch to ExclusiveFullScreen mode
4. Press '2' to switch to FullScreenWindow mode
5. Press Alt+Tab
Result: built Unity application remains maximized and positioned in front of other apps, even though the focus is shifted to other application
Reproduced in: 2018.3.0a5, 2018.4.1f1, 2019.1.4f1, 2019.2.0b4, 2019.3.0a4
Note1: on 2019 releases, alt tabbing occasionally results in orange tint applied to the screen for several milliseconds
Note2: 2017.4 scripting does not support screen mode switching
Note3: if switched from Windowed to FullScreenWindow, application behaves as intended
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [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
Add comment