Usability bug: handling of identities and contacts
|Reported by:||profo||Owned by:||thomasb|
I have three issues about the general usability of editing contacts and identities.
- Unify handling of contacts and identities
For two basically identical tasks (for the editing of a contact and for the editing of an identity) RC uses two different ways of editing:
1: A contact is edited righthandside of an abbreviated list of contacts.
2: An identity is edited below the complete list of identities.
Proposal: adopt the way of editing contacts for identities. The left side of the screen should show an abbreviated list of identities, the right side should display the complete identity settings on top of a watermark.
- Simplify browsing / editing
The current implementation is as follows:
Step 0: right hand side of the screen displays contact data in a "view only" mode. Below the contact data finds an "edit contact" button.
Step 1: Click the "edit contact" button
=> Page displays contact data with editable input fields
&& Page exchanges "edit contact" button with "cancel" and "save" buttons.
Step 2: Edit the contact data.
Step 3: Confirm or cancel edit by clicking appropriate button.
=> Page displays in "view" mode again
&& buttons changed back to "edit" button
I think it would be more intuitive (and more "ajax") to do the following:
Step 0: Right hand side displays the contact data with editable contact fields.
It shows inactive (greyed out) "save" and "cancel" buttons
Step 1: If some contact data is edited the buttons become active
Step 2: Confirm or cancel edit by clicking appropriate button.
=> buttons become inactive again
- Prevent data loss of edits
In both scenarios of B) the user should be prompted to save or discard the edits, if edits where made and the page is changed (by browsing another contact or redirecting to another url)
I hope you don't freak out by these comments, thanks in advance,
Change History (4)
comment:2 Changed 5 years ago by thomasb
- Component changed from Client Scripts to Core functionality
- Milestone changed from 0.2-beta to later