| 4c384ab3ae7621e602a95aeac6e527a52bb5598c |
|
21-May-2014 |
Régis Décamps <regisd@google.com> |
Let Rfc822Validator validate IEA in Punycode or Unicode.
Let Rfc822Validator validator internation email adresses.
The implementation is based on a regular expression.
Fixes:
- b/13364030 ComposeActivity rejects TLD that are Punycode
- ComposeActivity rejects TLD that are Unicode
Improve unit tests:
- Use RFC example domains, instead of potentially existing domains.
- Add unicode punycode internationalized email address.
- Add validity check for email with special characters.
- Add validity check "a..b@example.com" (RFC says dot cannot be succesive but it is allowed by major providers)
- Add invalidity check for "a@b-.com" (domain name cannot end with a dash) ; "john@doe@example.com" (@ must be unique)
- Remove a@b.12 from invalid emails. There is no tld made of numbers, but no spec strictly prohibits it.
Bug: 13364030
Change-Id: I78bc5d696f587753d776020ef1f9feded2065ad0
/frameworks/ex/common/tests/src/com/android/common/Rfc822ValidatorTest.java
|
| 490556a764a879cd0eaff358e90705cc1335c92e |
|
05-Aug-2011 |
Erik <epastern@google.com> |
b/5122753 Make Rfc822Validator a bit smarter
Change-Id: Iffea9735b906466077ce03a97ab49b614917dbf3
/frameworks/ex/common/tests/src/com/android/common/Rfc822ValidatorTest.java
|
| b4f5e0e5755938f2be9a2f1a1a6609b018c530ad |
|
30-Sep-2010 |
Paul Westbrook <pwestbro@google.com> |
Fixed the Rfc822Validator
Make sure that the validator doesn't consider an email address
that has a domain that has more than one adjacent '.' characters valid
Bug: 3048703
Change-Id: I1c227f393738850d89b6da52693d806c231f3136
/frameworks/ex/common/tests/src/com/android/common/Rfc822ValidatorTest.java
|