Closed Bug 1130901 Opened 5 years ago Closed 5 years ago
Method patching can cause permission denied errors from call-watcher
Found using WAE with: http://webaudiotool.com/app/?patch=1C170F35-3D45-0777-0EFF-8F3DFE42A3F1 since we proxy patch AudioContext methods, calling them via `call` or `apply` in content produces a permission denied error, like on this line: module.setAudioNode(this.audioContext[jsMethodName].call(this.audioContext, data.args)); This is due to the call-watcher actor, and will appear in the shader and canvas editor as well.
To clarify, this permission denied error breaks the entire functionality of the site with the tools open. Very very bad.
With the WAE tools open, and console, type in `(ctx = new AudioContext()).createOscillator.apply(ctx)` to see this.
Assignee: nobody → jsantell
Status: NEW → ASSIGNED
Tests pass for canvas and shader editor too. If there are any scenarios you think that are untested for these, let me know and I'll scope it out.
Attachment #8563125 - Flags: review?(vporof)
Attachment #8563125 - Flags: review?(vporof) → review+
You need to log in before you can comment on or make changes to this bug.