Andras,Thank you for testing.Maybe there's something different with our setups. To confirm that this wasn't caused by existing data. I delete all of the autofill data and added back one address. The issue is still present.I'm seeing it with:Iron Version 19.0.1100.0 (139545)Chromium Version 21.0.1180.0 (142701)Chrome Version 19 - 20.0.1132.34 betaAll OS XJust to clarify the issue for anyone else who might be interest in this. The problem only presents itself on the initial autofill. If I go back and edit the email (add a space to the end for example) angular recognizes it as a valid email. It appears that angular is not re-evaluating the field after autofill, therefore, it believes the field to be invalid.I went a head and filed an issue on the tracker. https://github.com/angular/angular.js/issues/1072I figured that with nearly 40% of all users using Chrome, even if only 1/2 of them experience this issue it make the email validation unusable.Thank you,Kyle
--
You received this message because you are subscribed to the Google Groups "AngularJS" group.
To view this discussion on the web visit https://groups.google.com/d/msg/angular/-/HK5zMjdW9vAJ.
Vojta, thank you for looking into this.I believe you are correct - Chrome is the issue here.When I first reported the problem I misdescribed it, I believe that's why it's difficult to reproduce. I've updated the Github issue with more information. Essentially the problem is Chrome's Autofill behavior not the tab complete. It is apparent that Chrome is using Autofill and not tab complete when the background color changes to yellow. For a user to be affected they must have saved Autofill information, therefore, the number of people affected will be smaller then I initially thought.Currently there are two workarounds:1. Remove method="POST" from the form - this will disable Autofill2. Manually fire the input event: $('#myform input,#myform select').on(function() { $(this).trigger('input'); }); as described by @robrbecker on Github
Angular's documentation does not include the method="POST" attribute in the form. As long as developers follow that example their users will not be affected by this.Thank you- Kyle
--
You received this message because you are subscribed to the Google Groups "AngularJS" group.
To post to this group, send email to ang...@googlegroups.com.
To unsubscribe from this group, send email to angular+u...@googlegroups.com.
Visit this group at http://groups.google.com/group/angular?hl=en.