3 ms·
Sorry, should have summarized changes: 1.6.1 addresses backwards compatibility issues with new 'attr()' and 'prop()' behaviour added in 1.6. This means that c
by tcarnell 15y ago
Sorry, should have summarized changes:
1.6.1 addresses backwards compatibility issues with new 'attr()' and 'prop()' behaviour added in 1.6.
This means that code written against 1.5.2 will work 100% against 1.6.1 (this was not the case with 1.6).
So to many people this is quite an important update.
- deleted 15y ago[deleted]
- crescentfresh 15y ago> 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.
- jeresig 15y agoActually == true and == false will still work, === true and === false will fail (as the return value is now "disabled" or undefined).
- crescentfresh 15y agoI meant, explicit checks on the return value will break (not that this is a bad thing). Specifically, neither `'disabled' == true` nor `undefined == false` will ever be true[thy] and are thus breaking changes. Perhaps you meant implicit conversions to boolean still working? Eg `!!'disabled'`, `if ('disabled')`, `!!undefined`, or `if (undefined)` will continue to work.