This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The AudioParam min and max values are expressed in floats, not doubles. createDelay should be changed accordingly, I think.
Actually, as much as possible I think we need to move to expressing all times in double-precision. But, you're right that they need to be made consistent.
Yeah. To be clear, I don't care about float vs. double that much, I just think consistency matters here.
Agree we should use doubles - see Bug 17393
Sounds good. I was changing this method in bug 19808 so I went ahead and changed in to float for now. We can take care of that when we fix bug 17393.
Should this be reopened, seeing as bug 17393 has been resolved? The current draft has createDelay as a double, but AudioParam min and max values are still float. Do we need any more changes before consistency is achieved?
My feeling was that the most urgent changes for doubles were with time values, where the precision is usually the most fiddly. We can also consider moving the rest to double
With bug 17393 reopened and dealing with the double/float issue in general, I think this can be closed.