That sounds right, except for audio worklets. No communication channel to avoid making these scripts depend on engine specifics? (Not entirely sure, it’s been a while.)
-
-
-
Audio worklets have both a bidirectional message channel and an event that fires on the AudioWorkletNode, but it's called "processorerror" (sort of), not "error"... and looks like it's not really defined what it really is. Filed https://github.com/WebAudio/web-audio-api/issues/1984 … on that.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.