Re: [whatwg] the impact of .value behavior clearing current selection prior to setting the new selection Cameron McCormack Wed, 01 Feb 2012 17:54:17 -0800 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 Previous message View by thread View by date Next message [whatwg] the impact of <select>.value behavior cle... Jon Lee Re: [whatwg] the impact of <select>.value beh... Ian Hickson Re: [whatwg] the impact of <select>.value... Cameron McCormack Re: [whatwg] the impact of <select>.v... Ian Hickson Reply via email to

[Cameron McCormack]

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