> code written against 1.5.2 will work 100% against 1.6.1
Nope. attr() returns a different value than it did before 1.6. Anything that relied on that value (eg $elem.attr('disabled') == true/false) is still going to break.
Nope. attr() returns a different value than it did before 1.6. Anything that relied on that value (eg $elem.attr('disabled') == true/false) is still going to break.
Perhaps you meant implicit conversions to boolean still working? Eg `!!'disabled'`, `if ('disabled')`, `!!undefined`, or `if (undefined)` will continue to work.