735232 - Input label is difficult on Chat account wizard

Status: NEW

(Thunderbird :: Instant Messaging, defect)

Description

[Tetsuharu OHZEKI [:tetsuharu] (UTC+9)]

Attachment: screen shot of Chat account wizard

Input label is difficult on Chat account wizard.
Users mistake the mean of a input field.

For example, if you add a facebook account, you need enter "Username" to input field. (See attachment screen shot)
But this label does not indicate the text which you should enter to field.
User may not understand the means of label.
Is it "username", "email", or the other one?

Same problem occurs on adding other services. (e.g. Twitter, Google Chat...)
I think that we should change labels into appropriate ones.

Comment 1

[Mark Banner (:standard8)]

Username is pretty standard terminology. We also use it in places where we ask for email as well, so I don't think there is much to improve on here.

Comment 2

[Tetsuharu OHZEKI [:tetsuharu] (UTC+9)]

(In reply to Mark Banner (:standard8) from comment #1)
> Username is pretty standard terminology. We also use it in places where we
> ask for email as well, so I don't think there is much to improve on here.

At the facebook case, We need enter a facebook's alias name to username field.
However, "username" label is used to enter email on Thunderbird commonly.
So this difference confuses users.
I think that better is adding following optional labels which is suited to each service:
"(You need enter facebook alias to username)"

Comment 3

[Florian Quèze [:florian]]

The facebook case is difficult, because whatever we write, users expect to be able to enter their email address (because that's what would make the most sense). Unfortunately, it's not what is required to authenticate with the Facebook XMPP server :(.

The term that the Facebook website consistently uses to refer to the string the user needs to enter is "username". Users can set it or find it (if it's already set) on the https://www.facebook.com/username/ page.

So saying "facebook alias" would be even more confusing.

In the future I would like us to attempt to authenticate with the Facebook servers through OAuth when the user has entered an email address in the username field, so that entering either the Facebook username or the email address commonly used to login to the facebook website would work.

Comment 4

[Tetsuharu OHZEKI [:tetsuharu] (UTC+9)]

(In reply to Florian Quèze from comment #3)
> The term that the Facebook website consistently uses to refer to the string
> the user needs to enter is "username". Users can set it or find it (if it's
> already set) on the https://www.facebook.com/username/ page.
> 
> So saying "facebook alias" would be even more confusing.

Yes. My analogy was wrong.

> In the future I would like us to attempt to authenticate with the Facebook
> servers through OAuth when the user has entered an email address in the
> username field, so that entering either the Facebook username or the email
> address commonly used to login to the facebook website would work.

I think its behavior is better.

So I wanted says, adding optional labels suited to each service prevents user's confusing...