[audioworklet] AudioWorkletGlobalScope not defined’s in console when adding the OT meta tag in head
Reported by
micbu...@gmail.com,
Jan 28 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36 Steps to reproduce the problem: 1. Go to https://wasabi.i3s.unice.fr/pedalboard, 2. Click on the synth tab 3. Drag'n'drop a synth into the pedalboard, open the devtool console, see the AudioWorkletGlobalScope error. Try with canary + flag, it works. What is the expected behavior? With the OT meta tag in the head of our index.html page, the webapp that uses AudioWorklets should run fine in Chrome stable. What went wrong? AudioWorklets work great in Chrome stable v64.0.3282.119 with Experimental Web Platform Features enabled in flags! (I joined origin trial, added the mailed meta tag to head but this results in ’AudioWorkletGlobalScope not defined’s in console. This happens during init stage, when sharing data between addModule() calls. The only difference between working / not working version is the added meta tag + disabling the flag. This is my first origin trial and I’m probably just missing something obvious. Any thoughts? Demo: https://wasabi.i3s.unice.fr/pedalboard Otherwise, with flag enabled, everything works fine. Did this work before? No Does this work in other browsers? No It can be tested only in Chrome as it's the only browser with AudioWorklet support. Chrome version: 64.0.3282.119 Channel: stable OS Version: OS X 10.12.6 Flash Version:
,
Jan 29 2018
,
Jan 29 2018
micbuffa@ Thanks for filing the issue! I will add one more important note: This demo loads the script file for Worklet from a different domain. I believe this remote domain is also white-listed by Origin Trial, but I am not sure how this cross-domain interaction is handled by Origin Trial and Worklet.addModule() method. Can you confirm this, micbufffa@?
,
Jan 29 2018
micbuffa@ FYI, the demo page is unreachable for the moment.
,
Jan 29 2018
,
Jan 29 2018
This CL might resolve this issue: https://chromium-review.googlesource.com/c/chromium/src/+/862257
,
Jan 29 2018
Ok, we're restarting the server. I'm really worried by what you said in the CL about external WC modules that use AW being loaded that could make some security error... We're just working on setting up a distributed architecture/open standard for WebAudio plugins based on the idea that they should be usable and inter operable through URLs...
,
Jan 31 2018
I ran a quick test using my local Chromium build that includes the CL referenced in #6: https://chromium-review.googlesource.com/c/chromium/src/+/862257 I don't see the error in the console vs running in Chrome M64. Also, in M64, after I drag/drop a synth, it does not seem to render completely. With my local build, I see the synth appear with a keyboard. If that sounds like expected behaviour, then it appears the CL has resolved the issue. micbuffa@ Would you be able to test your page with Chrome Canary to see if things are working as expected? If you have/install the latest canary (i.e. Jan 31 or later) it should include the CL.
,
Jan 31 2018
chasej@ I also locally confirmed the latest Canary fixes this issue. I pinged micbuffa@ and waiting for his verification. Thanks so much for fixing this!
,
Jan 31 2018
I confirm that the last Canary (Version 66.0.3335.0) runs the pedalboard app (https://wasabi.i3s.unice.fr/pedalboard/) with the OT meta tag, perfectly, and without the need to set any flag. Great work :-)
,
Jan 31 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Jan 28 2018