Bug 216814

Summary: OscillatorNode is not exposed
Product: WebKit Reporter: Marcin Wolniewicz <fuzzzym>
Component: Web AudioAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Major CC: cdumez, chrisguttandin
Priority: P2    
Version: Safari 14   
Hardware: All   
OS: All   

Marcin Wolniewicz
Reported 2020-09-22 00:39:52 PDT
Even though it looks like there was an attempt to expose an OscillatorNode constructor (https://bugs.webkit.org/show_bug.cgi?id=214746) it looks like it hasn't been in the end and AudioContext.createOscillator returns a WebKitOscillatorNode instead. Neither OscillatorNode or WebKitOscillatorNode prototypes (or constructors) are available in the global namespace. This issue breakes bindings when using Dart with dart2js.
Attachments
Chris Dumez
Comment 1 2020-09-22 15:47:53 PDT
*** This bug has been marked as a duplicate of bug 216163 ***
Chris Dumez
Comment 2 2020-09-22 15:49:03 PDT
(In reply to Marcin Wolniewicz from comment #0) > Even though it looks like there was an attempt to expose an OscillatorNode > constructor (https://bugs.webkit.org/show_bug.cgi?id=214746) it looks like > it hasn't been in the end and AudioContext.createOscillator returns a > WebKitOscillatorNode instead. Neither OscillatorNode or WebKitOscillatorNode > prototypes (or constructors) are available in the global namespace. This > issue breakes bindings when using Dart with dart2js. Yes, I temporarily regressed this while working on the unprefixed WebAudio API but fixed it shortly after in Bug 216163.
Marcin Wolniewicz
Comment 3 2020-09-23 00:26:08 PDT
Ok thanks! When will this be released to the public?
Chris Dumez
Comment 4 2020-09-23 08:24:28 PDT
(In reply to Marcin Wolniewicz from comment #3) > Ok thanks! When will this be released to the public? I am unable to comment on when a particular fix will be made public.
Note You need to log in before you can comment on or make changes to this bug.