W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2012

[whatwg] Time Parsing

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 12 Jan 2012 00:07:19 +0000 (UTC)
Message-ID: <Pine.LNX.4.64.1201112316400.26758@ps20323.dreamhostps.com>
On Wed, 11 Jan 2012, Ian Hickson wrote:
> On Wed, 15 Jun 2011, Lachlan Hunt wrote:
> > On 2011-06-15 07:55, Ian Hickson wrote:
> > > On Mon, 28 Mar 2011, Lachlan Hunt wrote:
> > > > This should also only allow up to 3 digits representing 
> > > > milliseconds. If there are 4 or more digits (microseconds or 
> > > > beyond), the spec should state that the remaining digits should be 
> > > > truncated.
> > > 
> > > Why?
> > 
> > Because the Date object can only handle precision to 3 decimal places, 
> > and implementations interpret times like "00:59:59.9999" as 
> > "00:59:59.999" instead of rounding it up to "01:00:00.000"
> 
> Fair enough. Done.

To elaborate, what I did was make it non-conforming, and define how to map 
fractional milliseconds to Date objects. I didn't actually make the 
parsing algorithm itself truncate the value, so theoretically if someone 
has non-conforming content with values with fractional milliseconds that 
is processed by software that isn't based on JS, it could still support 
those values.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 11 January 2012 16:07:19 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:10 UTC