Last modified: 2011-05-02 18:20:01 UTC
When filling out the email field, the field turns red or green depending on whether, at any given point in time, it looks like the email is valid for example, if I'm typing "myemail@address.com" and pause at "myemail", the field turns red. the issue with this behavior is that the user is told they're doing something wrong before they've completed the action. This has been observed on Chrome 10/OSX.
(In reply to comment #0) > When filling out the email field, the field turns red or green depending on > whether, at any given point in time, it looks like the email is valid > > for example, if I'm typing "myemail@address.com" and pause at "myemail", the > field turns red. > > the issue with this behavior is that the user is told they're doing something > wrong before they've completed the action. > This has been observed on Chrome 10/OSX. Can you please verify this against current trunk HEAD ? I very specifically bound the validation function to once('blur') and within that on keyup, which means: * When typing in an emailadres it won't mark it was invalid/red or valid/green the first time you enter it (ie. the first and in possibly only attempt). Instead it will do the first validation after you leave the emailaddres field (when you've completed the first attempt). At this point the field will either turn red or green. If and when the address field is adjusted after the first validation, it will validate after each key change. Green scenario: * User rates page, enters emailaddress, presses tab or whatever, sees mailaddress is ok (turns green), submits form. Red-then-green scenario: * User rates page, enters emailaddress, presses tab or whatever, sees mailaddress is invalid (turns red), user goes back and fixes it. After every key press the field is re-evaluated, it will stay red untill it's valid. When it is it turns green. User submits form. - Tested in Firefox 4 and Safari 5 on OS X. If you see that the field is turning red before finishing initial filling of the field, please re-open this bug.
