Closed Bug 1186514 Opened 9 years ago Closed 4 years ago

Take localization into consideration with Show/Hide string

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(firefox42 affected)

RESOLVED INCOMPLETE
Tracking Status
firefox42 --- affected

People

(Reporter: liuche, Assigned: antlam)

References

Details

Attachments

(1 file)

I was talking to rfeeley and tecgirl, and I learned that some languages can have very disparate string lengths for "Show" and "Hide". We should consider whether we should do something about our use of this (about:logins edit screen), whether it's using Show/Show, or iconography, or what.
Yeah, Ryan mentioned this. I think we should try to keep consistent with the work that's been happening on that side once a final decision has been made.
I feel like we should just use a different enabled state for the show button, similarly to what we do for the FxA login screen.
Anthony, have we settled on a solution for this? the fxA approach? The icon approach?
Flags: needinfo?(alam)
Not to my knowledge. But at the same time, I don't think there's an action item here right now. Did you have a string in mind for this bug that you wanted to correct?
Flags: needinfo?(alam) → needinfo?(ally)
Then we certainly need to settle on a solution before an engineer can implement anything. 

Our problem is that the single button for showing/hiding a password can be dramatically different lengths, screwing up the layout and giving the user a jarring & unpleasant experience. 

Switching between any two strings is going to have this problem in some locale(s), so we need either a single string approach or a no string approach.

Options include

= Making the button say something like "flip" or "Toggle", so that it is the same string regardless.

= Replacing Show/Hide entirely and use icons to signal show and hide.

= We reformat the page when the user pushes show or hide to accommodate the length of the word. I this this is the worst idea of the set, resulting in a disjoint and jarring experience. 

I'm open to other ideas. Perhaps Margaret or Barbara has some? Flod works with localizers, perhaps he has seen a novel approach to the problem.
Flags: needinfo?(margaret.leibovic)
Flags: needinfo?(francesco.lodolo)
Flags: needinfo?(bbermes)
Flags: needinfo?(ally)
Going to CC' Ryan Feeley here because I think he's been doing the most thinking about this and we should be keeping consistent.

Ryan, not a high priority but this is something we talked about in our passwords work. Any development here that we should be aware of?
Flags: needinfo?(rfeeley)
"Flip" or "Toogle" are a pain to translate, some languages don't have a single verb that expresses that concept, so you end up with ugly things like "Enable/disable", "Select/deselect", "Add/remove", etc.

The safer approach is usually to have a separate checkbox to "Show password". It embeds the concept of "toggle", and have plenty of space for longer translations.

See also bug 975013 about a similar issue.
Flags: needinfo?(francesco.lodolo)
We could take up more space and use a checkbox. I would love to do this as an experiment n FxA. Thoughts Vlad?
Flags: needinfo?(rfeeley) → needinfo?(vlad)
Note that it might get long. This is from the current password managed in Firefox desktop (not really sure why Polish has an entire sentence)
https://transvision.mozfr.org/string/?entity=toolkit/chrome/passwordmgr/passwordmgr.properties:showPasswordPlaceholder&repo=aurora
(In reply to Francesco Lodolo [:flod] from comment #10)
> Note that it might get long. This is from the current password managed in
> Firefox desktop (not really sure why Polish has an entire sentence)
> https://transvision.mozfr.org/string/?entity=toolkit/chrome/passwordmgr/
> passwordmgr.properties:showPasswordPlaceholder&repo=aurora

I think I'd support a layout where Show Password [x] is on a separate line below the password field. It's a single string solution that can handle a really long localized string with grace and doesn't suffer if the string is short.
This is true. The main reason we didn't opt for that is conventionally the 'Remember me' checkbox is there.
Flags: needinfo?(vlad)
Flags: needinfo?(margaret.leibovic)
For a simple fix, I think we should just follow the same pattern we use in the current FxA login screen (have a single "Show" button with an enabled/disabled state).

I don't think we need to try to invent a new UX pattern here, the main thing we're trying to fix is the fact that the "Hide" string can be a different length in other locales. It sounds like that's why Chenxia filed this bug.
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: