#13573 closed bug (duplicate)
checked property should be treated specially
Reported by: | lionel8000 | Owned by: | |
---|---|---|---|
Priority: | undecided | Milestone: | None |
Component: | attributes | Version: | 1.9.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
when I used elements.attr("checked",true) it works first time but when I used elements.attr("checked",true) after a call to elements.removeAttr('checked'); it will not work.
the reason is on line 2405 () of jquery-1.9.1.js before the code elem.removeAttribute( getSetAttribute ? name : propName ) is called the elem[propName] = false is called first,whick should be not called for the checked property.. SO the checked property should be treated specially
Change History (11)
comment:1 Changed 10 years ago by
Component: | unfiled → attributes |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
comment:2 Changed 10 years ago by
The jQuery 1.9 Upgrade Guide discusses this and the jQuery Migrate plugin warns about it. Every blog post since the 1.9 release in January pleads with people to read the upgrade guide and use the plugin. The download page emphasizes it as well.
Duplicate of #13245.