In Add Person form user is not able to navigate to next input field by pressing the [Tab] button in keyboard

[wasiqulhuq]

Perform following steps to reproduce,

1. Go to Add Person form
2. Click on Username input field and enter username
3. Press on [Tab] button in keyboard and observe that user is not navigated to the next input field in the form which is First Name field.

When user click on tab button in they expect to navigate to the next field in the form. In user self registration form in Gluu user is able to move between input fields by hitting the tab button which is expected.

Check below screen for detail information,

[shekhar16]

we fixed it in latest code commit on #861

[willow9886]

@shekhar16 tabs now work... but the new field you tab into is not selected...so the user still has to click from field to field!

[shekhar16]

The fields has been implemented with <rich:inplaceInput , so for every field we had span and input fields in combine form that's why, on focus its only focusing the field but not allowing to enter text.

[yurem]

In next version we are planning to remove richfaces at all. I think we can replace rich:inplaceInput with h:inputText to make text input generic across all our GUI.

[shekhar16]

[shekhar16]

Tabs are working to edit the textbox.

[natt-tester]

@shekhar16, I've just tested it and there seems to be quite a lot of buggy behavior present. Did you check the functionality after finishing the task?

Whenever I click on a field or use a tab, an error message pops out. Even as a reminder, it looks pretty aggressive, so without any real update/addition we shouldn't display them.

Also, the show/hide password icon doesn't seem to work.

And it's impossible to add a new user:

There's a typo, the string should be "Uid already exists".

The whole activity throws the following error:

Refer to the GIF:

[shekhar16]

@natt-tester

1. The primary validations are working on losing the focus on fields i.e if you leave the field blank and change focus from that fields it will validate immediately that's why u are seeing validation message popup.I think u should know about onfocus validations.

2. Show/hide buttons are not working because we are working on richfaces => primfaces migration i.e. Replace Richfaces with JSF2 and other JSF frameworks #768. And show/hide button already fixed in that branch, as this issue still in progress for other pages so we can't merged it right now.

3. We fixed the duplicate uid validation in 7fc02f4

@yurem i consolidated above changes in new PR (i.e. #1100 ) for above pending changes.So that u can merge it.

[natt-tester]

@shekhar16, great that there are some fixes provided. I always report what I see as a user, and at the moment of testing, the UX was terrible. "You know it works like that" doesn't really apply if we want to make the UX better.

I would suggest getting rid of the popup messages on focus out soon as possible, especially when the user clicks through them. The behavior in this view is inconsistent with other menu items' behavior, e.g. in Register Attribute. The way I see it, if there's any button that could validate the whole form -- just like Register does in this view -- it should do it, highlighting the field and/or providing a meaningful hint in/under the field + a pop-up: