- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 20 Dec 2012 17:54:04 +0000 (UTC)
- To: Mark Callow <callow.mark@artspark.co.jp>
- Cc: whatwg@whatwg.org, Jer Noble <jer.noble@apple.com>
On Thu, 20 Dec 2012, Mark Callow wrote: > On 2012/12/18 9:01, Ian Hickson wrote: > > On Tue, 2 Oct 2012, Jer Noble wrote: > >> The nature of floating point math makes precise frame navigation > >> difficult, if not impossible. Rob's test is especially hairy, given > >> that each frame has a timing bound of [startTime, endTime), and his > >> test attempts to navigate directly to the startTime of a given frame, > >> a value which gives approximately zero room for error. > > > > That makes sense. > > > > Should we add a preciseSeek() method with two arguments that does a > > seek using the given rational time? > > I draw your attention to "Don't Store that in a float > <http://randomascii.wordpress.com/2012/02/13/dont-store-that-in-a-float/>" > and its suggestion to use a double starting at 2^32 to avoid the issue > around precision changing with magnitude as the time increases. Everything in the Web platform already uses doubles. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 20 December 2012 17:54:31 UTC