19807 2012-11-01 00:01:32 +0000 The parameter to AudioContext.createDelay should be float, not double 2012-12-18 13:25:20 +0000 1 1 1 Unclassified AudioWG Web Audio API unspecified PC All CLOSED FIXED P2 normal TBD 1 ehsan crogers mage olivier.thereaux public-audio oldest_to_newest 77619 0 ehsan 2012-11-01 00:01:32 +0000 The AudioParam min and max values are expressed in floats, not doubles. createDelay should be changed accordingly, I think. 77620 1 crogers 2012-11-01 00:06:55 +0000 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. 77626 2 ehsan 2012-11-01 00:24:49 +0000 Yeah. To be clear, I don't care about float vs. double that much, I just think consistency matters here. 77636 3 mage 2012-11-01 07:39:07 +0000 Agree we should use doubles - see Bug 17393 77676 4 ehsan 2012-11-01 15:34:26 +0000 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. 78470 5 olivier.thereaux 2012-11-19 16:01:50 +0000 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? 78481 6 crogers 2012-11-19 18:26:48 +0000 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 80347 7 olivier.thereaux 2012-12-18 13:25:20 +0000 With bug 17393 reopened and dealing with the double/float issue in general, I think this can be closed.