Settings: Users: Provide correct email in API

chrome/common/extensions/api/users_private.idl

Index: chrome/common/extensions/api/users_private.idl
diff --git a/chrome/common/extensions/api/users_private.idl b/chrome/common/extensions/api/users_private.idl
index 8d01f52865c1b4cdabc7144e7efd1794e9ab9853..702cf53c3629a9639c06009550129ae08cb15ef8 100644
--- a/chrome/common/extensions/api/users_private.idl
+++ b/chrome/common/extensions/api/users_private.idl
@@ -11,6 +11,9 @@ namespace usersPrivate {
     // Email for the user.
     DOMString email;
 
+    // Display email for the user.

[tommycli, 2017/05/17 15:56:12]

nit: Maybe "Displayed email" so it's not confused for a verb. Same with comment
on "Displayed name" too

[stevenjb, 2017/05/17 16:05:34]

Hmm, I feel like "display name" (and equivalent "display email") is the more
common usage (276 results for "display name" in chrome code vs. 8 for "displayed
name"; "display email" is less common but still twice as common as "displayed
email"), despite the potential for confusion (gotta love English). "Displayed"
has it's own problems (it hasn't actually been displayed anywhere yet), and "The
email address to use for display purposes" just sounds silly :)

[Devlin, 2017/05/17 16:16:14]

If we *really* wanted to bikeshed this, "emailForDisplay" or "nameForDisplay" is
probably most accurate.  But I agree with Steven that, in this case, consistency
is probably more useful.  Maybe we can keep the variables the same and just
update these comments, "Display-friendly email for the user" or something
similar?

+    DOMString displayEmail;
+
     // Display name for the user.
     DOMString name;