Thanks for your contribution!
The code review on the autoplay part will take some time because the WebAudio owners will need to understand the actual implementation.
It generally looks good, but I am curious about your evaluation plan on the rollout other than using usage counters.
"Cannot suspend a closed AudioContext."));Perhaps we can expand this error message to be more descriptive?
CONSOLE WARNING: The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://developer.chrome.com/blog/autoplay/#web_audioCan you explain why this CONSOLE WARNING is shown here?
const timeout = new Promise(resolve => setTimeout(resolve, 500));I am not entirely sure what test is verifying. (The autoplay code is not implemented by the WebAudio team)
If the intention is to get the state reliably, I think we can use the `onstatechange` event listener within the promise.
await context3.resume();Is this necessary to pass the test?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |