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
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
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
On Mon, 28 Mar 2011, Lachlan Hunt wrote:
The algorithm to parse a time component contains a bug.
When parsing the seconds, the spec states:
Collect a sequence of characters that are either characters in the
range U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9) or U+002E FULL
