W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2009

[whatwg] HTMLOptionElement::value compatibility

From: TAMURA, Kent <tkent@chromium.org>
Date: Mon, 3 Aug 2009 13:44:32 +0900
Message-ID: <b7b4ecf80908022144l31c1a11o2bd11546a2cad084@mail.gmail.com>
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.

-- 
TAMURA Kent
Software Engineer, Google



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090803/b45a2ee3/attachment-0001.htm>
Received on Sunday, 2 August 2009 21:44:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:51 UTC