- From: Kartikaya Gupta <lists.whatwg@stakface.com>
- Date: Mon, 03 Aug 2009 19:26:13 +0000
On Mon, 3 Aug 2009 07:09:26 +0000 (UTC), Ian Hickson <ian at hixie.ch> wrote:
> On Thu, 23 Jul 2009, Kartikaya Gupta wrote:
> >
> > The description for what to do on setting valueAsNumber doesn't fully
> > cover error conditions. It's not clear to me, for instance, what's
> > supposed if you have an input type="date" or type="number" and try to
> > set valueAsNumber to NaN. The description there (for date) just says
> > "... passing it a Date object whose time value is the new value ..." but
> > doesn't say what to do if the Date object can't be created.
>
> # Unless otherwise specified, if a DOM attribute that is a floating point
> # number type (float) is assigned an Infinity or Not-a-Number value, a
> # NOT_SUPPORTED_ERR exception must be raised.
> -- http://www.whatwg.org/specs/web-apps/current-work/#dependencies
>
Ah, thanks.
>
> > Also, editorial fix: in the same two paragraphs ("On getting" and "On
> > setting" for valueAsNumber), the link to valueAsDate is wrong; it just
> > links back to #dom-input-valueAsNumber instead of
> > #dom-input-valueAsDate.
>
> It appears I already fixed that already.
>
It's still wrong for me. Search for the string "Otherwise, if the valueAsDate" in the spec. There should be two occurrences; in both of them the "valueAsDate" links to #dom-input-valueAsNumber.
kats
Received on Monday, 3 August 2009 12:26:13 UTC