Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X
Votes
4
Found in
2020.1.0a16
2021.1
2021.2
2021.2.0b1
2022.1
Issue ID
1347304
Regression
Yes
[WebGL] Fullscreen mode does not expand the Player's window fully and has black edges when using Safari
How to reproduce:
1. Open the attached project
2. Make a WebGL build
3. Host the built WebGL Player locally
4. Open the WebGL Player on Safari
5. Click the expand button (marked as diagonal arrows)
6. Inspect the fullscreen mode
Expected result: Player's window is expanded fully and there are no black edges
Actual result: Player's window is not expanded fully and there are black edges
Reproducible with: 2020.1.0a16, 2020.14f1, 2021.1.16f1, 2021.2.0b4, 2022.1.0a2
Not reproducible with: 2019.4.29f1, 2020.1.0a15
Couldn't test with: 2020.3.14f1 (due to "Fullscreen is not supported on this browser." error from case 1287346)
Notes:
- Tested with Safari 14.1.1 on macOS 11.4
- Not reproducible on Chrome, Firefox
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2022.1):
Fullscreen mode on Safari will now correctly stretch the canvas to fill the screen. Fixed in Unity 2022.1.0a7 and above.
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.5f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.25f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.34f1