Change return type to w3c standard of void for AudioBufferCallback.

lib/html/idl/dart/dart.idl

 
 // This file introduces / supplements and forces Dart declarations.
 
 module default {
   ClientRectList implements sequence<ClientRect>;
   CSSRuleList implements sequence<CSSRule>;
   CSSValueList implements sequence<CSSValue>;
   DOMMimeTypeArray implements sequence<DOMMimeType>;
   DOMPluginArray implements sequence<DOMPlugin>;
   EntryArray implements sequence<Entry>;
@@ skipping 373 matching lines @@
 }
 
 module core {
   [Supplemental, Callback]
   interface RequestAnimationFrameCallback {
     // Webkit implements this as returning bool, but standard is void.
     [Suppressed] boolean handleEvent(in DOMTimeStamp time);
     [Custom] void handleEvent(in DOMTimeStamp time);
   };
 }
+
+module audio {
+  [Supplemental, Callback]
+  interface AudioBufferCallback {
+    // Webkit implements this as returning bool, but standard is void.
+    [Suppressed] boolean handleEvent(in AudioBuffer audioBuffer);

[Anton Muhin, 2012/10/16 09:41:09]

just a thought: do we have use cases when callback should return bool indeed?

Maybe we should switch default and treat callbacks as void unless a special
annotation is added.

WDYT?

[podivilov, 2012/10/16 11:45:43]

Looks like generated WebKit bindings always ignore the value returned from
JavaScript. I strongly suspect we should just switch to void for all the
callbacks instead of adding suppressions to dart.idl.

+    [Custom] void handleEvent(in AudioBuffer audioBuffer);
+  };
+}