Closed Bug 805031 Opened 13 years ago Closed 13 years ago

[email] New account signup field prefills "gmail", hiding what the field is for

Categories

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

defect
Not set
normal

Tracking

(blocking-basecamp:-)

VERIFIED FIXED
blocking-basecamp -

People

(Reporter: wenzel, Unassigned)

References

Details

(Keywords: b2g-testdriver, polish, unagi, Whiteboard: interaction, UX-P3)

Attachments

(1 file)

after unboxing, click on email, choose "gmail account" The top field says "name", the bottom field says "password" and the middle field is prefilled with "gmail.com" (sic). It takes some prior knowledge to realize you're supposed to edit that field and put "myusername@" before the "gmail.com" I suggest just not putting anything into the field. If people put only their username in it, add @gmail.com internally. If people put the whole thing into it, great.
Attached image Screenshot
Screenshot of the issue.
blocking-basecamp: --- → ?
This is confusing, and there are a few dupes, but it's not enough to block the release.
blocking-basecamp: ? → -
Keywords: polish
Component: Gaia → Gaia::E-Mail
The input fields should have labels describing the input field: Account name [input field] Gmail Username [input field] Password [input field]
Whiteboard: [interaction]
Priority: -- → P2
Severity: enhancement → normal
Priority: P2 → --
Whiteboard: [interaction] → interaction, UX-P3
Couldn't figure out how to set up my mail until I found the description in this bug of what to do with the unlabeled second field (I assumed it was 'server' and didn't need anything else filled in). Note that Google Mail accounts do not necessarily end in @gmail.com -- they may be Google Apps addresses or others.
This is fixed with the patches landed on bug 809552. We tried doing the labeled inputs as per comment 3, but screen real estate concerns made us bail on that in favor of just using placeholders.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Veified as fixed with Unagi, build ID 20120102070202
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: