Closed colinbdclark closed 6 years ago
Hi, @colinbdclark. A quick look through the Chromium command-line options suggests that we have a few ways to enable autoplay. You should be able to add one or more of those new flags to the browser args in your testem.json file. I linked to the one I'd start with if I were you, --no-user-gesture-required
.
Sadly --no-user-gesture-required
, as well as any of the other apparently appropriate flags, don't work. The one above, fortunately, does. I'll submit a PR shortly.
As mentioned by @the-t-in-rtf on #224, Flocking's Web Audio API-related tests have started failing on Chrome due to the implementation of its new autoplay policies. The error is:
Since unit tests need to run without any user intervention, the only solution I can think of to address this is to ensure that testem sets the appropriate command line flag to disable the autoplay policy when launching Chrome. The (only) relevant flag that works is: