RESOLVED FIXED 69182
BiquadFilterNode .type attribute is not handled correctly
https://bugs.webkit.org/show_bug.cgi?id=69182
Summary BiquadFilterNode .type attribute is not handled correctly
Chris Rogers
Reported 2011-09-30 16:14:14 PDT
BiquadFilterNode .type attribute is not handled correctly
Attachments
Patch (24.03 KB, patch)
2011-09-30 17:06 PDT, Chris Rogers
kbr: review+
Chris Rogers
Comment 1 2011-09-30 17:06:06 PDT
Kenneth Russell
Comment 2 2011-10-03 10:55:57 PDT
Comment on attachment 109375 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=109375&action=review Looks fine overall; couple of comments. r=me > LayoutTests/webaudio/biquadfilternode-basic.html:29 > + // FIXME: we need to expose the actual filter type constants in the IDL Have you already filed a bug about this? > LayoutTests/webaudio/biquadfilternode-basic.html:38 > + for (var i = 0; i <= 7; ++i) { FIXME for the magic constant 7. > Source/WebCore/platform/audio/AudioDSPKernelProcessor.cpp:61 > + m_hasJustReset = true; Is this fix really related or should it be a separate change?
Chris Rogers
Comment 3 2011-10-03 12:12:26 PDT
Chris Rogers
Comment 4 2011-10-03 12:15:11 PDT
Comment on attachment 109375 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=109375&action=review >> LayoutTests/webaudio/biquadfilternode-basic.html:29 >> + // FIXME: we need to expose the actual filter type constants in the IDL > > Have you already filed a bug about this? Just filed: https://bugs.webkit.org/show_bug.cgi?id=69276 >> LayoutTests/webaudio/biquadfilternode-basic.html:38 >> + for (var i = 0; i <= 7; ++i) { > > FIXME for the magic constant 7. added FIXME here >> Source/WebCore/platform/audio/AudioDSPKernelProcessor.cpp:61 >> + m_hasJustReset = true; > > Is this fix really related or should it be a separate change? It's related since, it's required when changing filter types. The filter state needs to be reset...
Boris Smus
Comment 5 2011-10-04 13:26:46 PDT
Thanks for fixing. Verified in Canary.
Note You need to log in before you can comment on or make changes to this bug.