I noticed the following bug when using $(selector).children().attr("disabled", "disabled")
where the children happened to contain a <div>
.
<div disabled="disabled">
<input type="text" value="RAGE" />
</div>
Basic testing says FF4/Chrome enable the field. IE9 disables the field.
What is the expected behaviour?
Same for any other non form element (<input>
, <select>
, etc)
There is no
disabled
attribute for thediv
element. So it should have no effect.<div>
elements do not have adisabled
attribute according to the HTML specification. The expected behavior is to prevent your markup from validating correctly.However, the new HTML5 specification allows for
<fieldset>
to have adisabled
attribute, which disables any nested input fields. It's not widely supported yet though, so you won't be able to rely on this feature for a while.