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 20589 - reconsider the type of SpeechSynthesisEvent.elapsedTime
Summary: reconsider the type of SpeechSynthesisEvent.elapsedTime
Status: RESOLVED WONTFIX
Alias: None
Product: Speech API
Classification: Unclassified
Component: Speech API (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Glen Shires
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-07 21:03 UTC by Trevor Saunders
Modified: 2013-01-31 21:21 UTC (History)
4 users (show)

See Also:

Attachments

Description Trevor Saunders 2013-01-07 21:03:45 UTC 
Olli says he thinks float is the wrong type and I think I agree its suboptimal.  It might also be better to use miliseconds than seconds.
Comment 1 Glen Shires 2013-01-08 05:15:22 UTC 
float was chosen for consistency with currentTime in a HTMLMediaElement. [1]  (There's also some additional discussion on this topic in other emails in that thread.)

If you have an alternative suggestion, please make a specific proposal.

[1] http://lists.w3.org/Archives/Public/public-speech-api/2012Oct/0001.html
Comment 2 Dominic Mazzoni 2013-01-14 21:11:49 UTC 
I like it how it is, consistency with HTMLMediaElement makes sense - that's the only other place in the HTML5 spec where elapsed time of multimedia is found.
Comment 3 chris fleizach 2013-01-23 19:56:39 UTC 
implementing and using elapsed time as a float seemed natural to me. i also liked having it in seconds, which is a natural base to use. when dealing in milliseconds you always end up making a mistake and then having to fix it
Comment 4 Olli Pettay 2013-01-31 21:21:29 UTC 
The platform is in no way consistent with time handling.
setTimeout etc use milliseconds but looks like Audio API has seconds.
I guess I can live with float.