[whatwg] HTMLOptionElement::value compatibility

Ian Hickson ian at hixie.ch
Wed Aug 12 00:43:28 PDT 2009

On Mon, 3 Aug 2009, TAMURA, Kent wrote:
> The `value' DOM attribute of HTMLOptionElement is incompatible with the
> current major browsers.
> The spec says:
> http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html#dom-option-value
> <http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html#dom-option-value>
>   The disabled, label, and value DOM attributes must
> reflect<http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.html#reflect>
> the
> respective content
>   attributes of the same name.
> However .value in IE8, Firefox3.5, Chrome2, Safari4, and Opera10b2 doesn't
> work so.  It returns the value of `value' HTML attribute, or the value of
> .text DOM attribute if the element doesn't have the `value' HTML attribute
> or the value of `value' HTML attribute is empty.  If we substitute a string
> to .value DOM attribute, the `value' HTML attribute is updated.
> The spec should follow this behavior.

Thanks, fixed.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

More information about the whatwg mailing list