Closed Bug 767610 Opened 8 years ago Closed 2 years ago

Validate email address format in call to navigator.id.watch and Identity.jsm _discoverIdentityProvider

Categories

(Core Graveyard :: Identity, enhancement)

enhancement
Not set
normal

Tracking

(blocking-basecamp:-)

RESOLVED INCOMPLETE
blocking-basecamp -

People

(Reporter: MattN, Unassigned)

References

()

Details

This will help RPs catch bugs in their code. It can be null/undefined or a valid email address.  We should probably make nsHTMLInputElement::IsValidEmailAddress accessible somewhere and use it.
(In reply to Matthew N. [:MattN] from comment #0)
> This will help RPs catch bugs in their code. It can be null/undefined or a
> valid email address.  We should probably make
> nsHTMLInputElement::IsValidEmailAddress accessible somewhere and use it.

Note that nsHTMLInputElement::IsValidEmailAddress is checking that the email address is following HTML5 definition of an email address. This is not exactly the same definition as the RFC.
This would also be good to have for _discoverIdentityProvider in Identity.jsm
Summary: Validate email address format in call to navigator.id.watch → Validate email address format in call to navigator.id.watch and Identity.jsm _discoverIdentityProvider
this will be handled in the server-provided dialog logic, so not basecamp blocking
blocking-basecamp: --- → -
See https://bugzilla.mozilla.org/show_bug.cgi?id=1497358; closing remaining open bugs in this component.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.