@curious.jp I’ve encountered the bug several times too! I tried to reproduce it intentionally, no luck.
Try to refresh your Bunpro tab by hitting Ctrl+R. Maybe it caused by an old version of the frontend bundle.
Nitty-gritty technical details for Bunpro staff:
it happens because a <div> container of the audio player have .native-audio class sometimes when a review session begins, but the audio player only supposed to have this class. And it crashes because <div>'s don’t have play() method of course.
But I can’t figure out how that class ends up there.
I have updated the way that we check to look specifically for an audio element. Hopefully that helps!









