Side navigation
#10073 closed bug (worksforme)
Opened August 17, 2011 01:30PM UTC
Closed August 18, 2011 06:38AM UTC
attr('disabled') always return undefine
| Reported by: | Vitaliy Medvedev, medvedev.vs@gmail.com | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | None |
| Component: | attributes | Version: | 1.6.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
attr('disabled') always return undefined - http://jsfiddle.net/ZSnn8/
compare with results in jquery 1.6.0 - http://jsfiddle.net/bDXvK/
Attachments (0)
Change History (1)
Changed August 18, 2011 06:38AM UTC by comment:1
| component: | unfiled → attributes |
|---|---|
| priority: | undecided → low |
| resolution: | → worksforme |
| status: | new → closed |
This has been fixed in jQuery (edge). I've verified that at least in Chrome 13 with 1.6.2, undefined is returned for attr('disabled') (using the examples cited) but 1.6.3 should contain the fix as long as it isn't backed out.
I haven't been able to locate the commit responsible for this, but here's a test case using edge that shows your example working fine: http://jsfiddle.net/znyvN/.
(Note: I don't consider this a dupe of #9927 as there are confirmed diffs between 1.6.2 and edge, whilst that ticket specifically deals with the pre/post 1.6.x prop/attr issues).