Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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)
<div>elements do not have adisabledattribute 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 adisabledattribute, 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.