Side navigation
#13573 closed bug (duplicate)
Opened March 06, 2013 11:19AM UTC
Closed March 06, 2013 12:34PM UTC
Last modified October 18, 2013 01:28PM UTC
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
Attachments (0)
Change History (11)
Changed March 06, 2013 12:34PM UTC by comment:1
| component: | unfiled → attributes |
|---|---|
| resolution: | → duplicate |
| status: | new → closed |
Changed March 06, 2013 01:59PM UTC by comment:2
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.
Changed October 13, 2013 12:25PM UTC by comment:10
#14416 is a duplicate of this ticket.
Changed October 18, 2013 01:28PM UTC by comment:11
#14461 is a duplicate of this ticket.
Duplicate of #13245.