You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 18, 2022. It is now read-only.
Chromium x64 version 62.0.3202.89 on Arch Linux 4.13.11
Chromium has a great hidden feature in chrome://flags that allows to disable autoplay, when setting the Autoplay policy flag to Document user activation is required and restarting. But the music on this app does not start playing, and the following warning is shown in the developer tools :
An AudioContext in a cross origin iframe must be created or resumed from a user gesture to enable audio output. (Song @ bundle.js:14055)
If possible, there should be a way to start it manually, or at least to detect that autoplay is disabled and ask the user to enable it.
The text was updated successfully, but these errors were encountered:
I am sure it's possible. But using the Chrome flags, which are experimental features, is an extreme edge case. Not sure if devs on this project have time for those kind of edge cases. If you want you could submit a pull request with the fix!
Chromium x64 version 62.0.3202.89 on Arch Linux 4.13.11
Chromium has a great hidden feature in
chrome://flags
that allows to disable autoplay, when setting the Autoplay policy flag to Document user activation is required and restarting. But the music on this app does not start playing, and the following warning is shown in the developer tools :An AudioContext in a cross origin iframe must be created or resumed from a user gesture to enable audio output. (Song @ bundle.js:14055)
If possible, there should be a way to start it manually, or at least to detect that autoplay is disabled and ask the user to enable it.
The text was updated successfully, but these errors were encountered: