This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 19807 - The parameter to AudioContext.createDelay should be float, not double
Summary: The parameter to AudioContext.createDelay should be float, not double
Status: CLOSED FIXED
Alias: None
Product: AudioWG
Classification: Unclassified
Component: Web Audio API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: TBD
Assignee: Chris Rogers
QA Contact: public-audio
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-01 00:01 UTC by Ehsan Akhgari [:ehsan]
Modified: 2012-12-18 13:25 UTC (History)
2 users (show)

See Also:

Attachments

Description Ehsan Akhgari [:ehsan] 2012-11-01 00:01:32 UTC 
The AudioParam min and max values are expressed in floats, not doubles.  createDelay should be changed accordingly, I think.
Comment 1 Chris Rogers 2012-11-01 00:06:55 UTC 
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.
Comment 2 Ehsan Akhgari [:ehsan] 2012-11-01 00:24:49 UTC 
Yeah.  To be clear, I don't care about float vs. double that much, I just think consistency matters here.
Comment 3 Marcus Geelnard (Opera) 2012-11-01 07:39:07 UTC 
Agree we should use doubles - see Bug 17393
Comment 4 Ehsan Akhgari [:ehsan] 2012-11-01 15:34:26 UTC 
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.
Comment 5 Olivier Thereaux 2012-11-19 16:01:50 UTC 
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?
Comment 6 Chris Rogers 2012-11-19 18:26:48 UTC 
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
Comment 7 Olivier Thereaux 2012-12-18 13:25:20 UTC 
With bug 17393 reopened and dealing with the double/float issue in general, I think this can be closed.