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

[whatwg] the impact of <select>.value behavior clearing current selection prior to setting the new selection

From: Cameron McCormack <cam@mcc.id.au>
Date: Thu, 02 Feb 2012 12:53:52 +1100
Message-ID: <4F29ECB0.2000507@mcc.id.au>
Ian Hickson:
> It's my understanding that what you describe as what browsers do is also
> what the specs require. The attribute is defined as being of type "long",
> so if I'm not misreading the Web IDL spec, the browser will try to convert
> the null or string value to a number (and fail) long before the HTML
> spec's prose is relevant.

For the long type, null and strings like "junk" will get converted to 0.

http://dev.w3.org/2006/webapi/WebIDL/#es-long
Received on Wednesday, 1 February 2012 17:53:52 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:39 UTC