Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.4
2019.3.10f1
2020.2
Issue ID
1241584
Regression
No
[WebGL] [VideoPlayer] Autoplay of muted video is blocked when 'Wait For First Frame' option is disabled in the VideoPlayer
Reproduction steps:
1. Open the attached project ("case_1241584-MutedVideos.zip")
2. Open the repro scene ("SampleScene")
3. Select the "Video Player" object and inspect that "Wait For First Frame" is disabled
4. Also, inspect that "Audio Output Mode" is set to "Direct". with 1 Controlled Track with Mute checkbox checked
5. Put the "180p-h264.mp4" video somewhere where it can be accessed via URL and set the correct URL in the Video Player
6. Make a WebGL build and run it without interacting with the page
Expected result: Video autoplay succeeds as it does not have audio
Actual result: Video autoplay is blocked by the browser's policy; DOMexceptions are thrown on Chrome
Reproducible with: 2018.4.14f1, 2019.4.1f1, 2020.1.0b13, 2020.2.0a15
Tested with: Chrome (83.0.4103.106), Firefox (77.0.1)
Notes:
1. Enabling "Wait For First Frame" fixes the issue
2. Setting "Audio Output Mode" to "None" also reproduces the issue when of "Wait For First Frame" is off
3. The issue does not reproduce on Edge as it supports autoplay of non-muted videos
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
- Incorrect vehicle rotation when using ForceMode.VelocityChange
- [Linux] Dropdown Menus are filled with empty entries when the Menu intersects with the Editors borders
- [HDRP] [Metal] Tiled artefacts when using DRS
- [HDRP] Empty template starts with incorrect Physically Based Sky ground
- Big chunk of "Untracked" memory in the Memory Profiler screenshot when a custom .obj file is loaded while in Play Mode
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a18