#9576 closed bug (invalid)
removeAttr("disabled") on IE7
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | low | Milestone: | 1.next |
Component: | attributes | Version: | 1.5.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
BUG only on IE7 (FF and IE8 and IE9 is OK)
Sample :
$("#id_rectif_mail :input").removeAttr("disabled");
id_rectif_mail is a DIV
If i select each input then removeAttr("disabled") is OK .
Thanks in advance
Change History (7)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
Component: | unfiled → attributes |
---|---|
Owner: | set to [email protected]… |
Priority: | undecided → low |
Status: | new → pending |
Thanks for taking the time to contribute to the jQuery project! Please provide a reduced test case on http://jsfiddle.net that reproduces the issue experienced to help us assess your ticket.
Additionally, test against the jQuery (edge) version to ensure the issue still exists.
comment:3 Changed 12 years ago by
Resolution: | → invalid |
---|---|
Status: | pending → closed |
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
comment:5 Changed 12 years ago by
Replying to anonymous:
Running IE8 in IE7 browser mode this error happens:
On jQuery 1.6.2, that is. It works fine on 1.6.1
comment:6 Changed 12 years ago by
@anonymous: see #9719 As you can see, jQuery is doing everything it can. IE7 is not repainting: http://jsfiddle.net/timmywil/yjsqc/4/
comment:7 Changed 11 years ago by
I have also found that under certain hard-to-reproduce conditions .removeAttr('disabled') does not do the right thing in IE7. One very simple way around this is to use .prop('disabled', false) instead.
In fact, this is the TEXTAREA in the "ui dialog" that generate this bug , I think, and only on ie7 .