559741 - Wrong validation of email field

Status: RESOLVED INVALID

(Websites :: creative.mozilla.org, defect)

Description

[Ayan Shah[:ashah]]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9 (.NET CLR 3.5.30729)

In the forgot password page, we have to enter the email address to retrieve a forgotten password. Now I entered junk.junk@junk. It should have been validated on the client side and should have said that please enter a valid email address. Instead it did post back to the server side and said that "No accounts are associated with this email address". Instead it should have said - "Please enter correct email"

Reproducible: Always

Steps to Reproduce:
1.Go to https://creative.mozilla.org/forgot
2. enter junk.junk@junk in the Your email address field. 
3. Press Send link. 
Actual Results:  
It displays "No accounts are associated with this email address".

Expected Results:  
It should have been validated on the client side and should have said - "Please enter a valid email address".

Comment 1

[Boris Zbarsky [:bzbarsky]]

This has nothing to do with the DOM.

Further, junk.junk@junk is a valid e-mail address.  So the behavior is even correct.

Comment 2

[Ayan Shah[:ashah]]

Do you expect the email to be delivered when I write junk.junk@junk?
No. Thats because the .com/.org/.edu suffixes are missing. So thats not a valid address. So before going to the server side, you should check on the client side for the validation of correct format of email address. That prevents a round trip to server and saves network traffic.

Comment 3

[Boris Zbarsky [:bzbarsky]]

> Do you expect the email to be delivered when I write junk.junk@junk?

Yes, if there is a server named junk in my default search path and it's hosting mail.  For example, junk.mit.edu in my case.  junk.gmail.com in yours, probably.

> Thats because the .com/.org/.edu suffixes are missing.

I really suggest looking up how hostname resolution works...

> So thats not a valid address.

Sorry, it is.  It's just not globally defined in the sense that its destination server depends on the current lookup path.  Then again, so does gmail.com (e.g. "gmail.com" would resolve to gmail.com.mit.edu for me if MIT handed out .com.mit.edu subdomains).  If you really want to ensure global uniqueness, you need the '.' at the end (e.g. "gmail.com." will always mean the "gmail" subdomain of the "com" toplevel domain).