You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, in-app error message is more specific than the constraint in mentioned in the UG. They mean the same thing (i.e. format should be [email protected], where xxx, yyy, zzz are valid parts of an email) and hence there is no conflict.
Second, we decided not to put everything in the UG, because putting every constraint in the UG hinders the reader as it provides too much information, while the user only needs to know roughly what it means to be a valid email. In our opinion, the amount of information we put there is appropriate for the reader. We decided to put all the details related to email constraint only in the app in case the user accidentally keys in a wrong email address and needs to see why.
Items for the Tester to Verify
❓ Issue response
Team chose [response.Rejected]
I disagree
Reason for disagreement: [replace this with your explanation]
UG and Email warning message constraints do not match which might confuse users as to which constraints to follow.
The text was updated successfully, but these errors were encountered: