-
Notifications
You must be signed in to change notification settings - Fork 27.4k
jQuery migrate 1.1.0 shows warnings with angularjs 1.1.5 in various places #4107
Comments
A full list would be really helpful. A pull request with fixes would be even better! |
Sorry, I’ve only run into the one I listed in the description at present, but presumably anywhere else in the code that uses $.attr() would cause similar migration warnings. From: Pete Bacon Darwin [mailto:notifications@github.com] A full list would be really helpful. A pull request with fixes would be even better! — |
The |
Closing in favour of #4122 |
jQuery suggests using `prop` rather than `attr` to modify the `select` property of an element. You can see the full list of migration warnings for jQuery: https://github.com/jquery/jquery-migrate/blob/master/warnings.md Closes angular#4107 Closes angular#4122
jQuery suggests using `prop` rather than `attr` to modify the `select` property of an element. You can see the full list of migration warnings for jQuery: https://github.com/jquery/jquery-migrate/blob/master/warnings.md Closes #4107 Closes #4122
For example;
"jQuery.fn.attr('selected') may use property instead of attribute"
The text was updated successfully, but these errors were encountered: