New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve the layout of the contacts app with single column list view and other changes #2699
Comments
|
A linear layout (like in the iCloud screenshots) would also fix the annoyance of the form elements moving around as you add or remove contact properties. |
|
Related #1923 |
|
@arnowelzel, potentially rename this issue so that it demonstrates that the priority, if not sole problem that it demonstrates, is that the fields should be presented as a list, because locating this was difficult, so I almost created a duplicate for a list-view of forms. |
|
@BEEDELLROKEJULIANLOCKHART Using a list instead of multicolumn is not the only problem. But I changed the issue to reflect the single column approach. But please read the section "Describe the solution you'd like" to understand that using a single column is not the only proposed change. |
|
I am just testing a fresh install of NC 25.0.1 and found the contacts app layout to be even worse than before. |
|
Since it seems to take a while until this is fixed, I started working on a workaround using CustomCSS. So far I added the following rules to achieve the following goals:
The result is not perfect yet and will not work nicely on mobile devices since labels and input element should be placed in a different way there - but it is still much easier to use than before in my opinion and one might add a media selector for mobile devices as well to cope with that. Update 2023-03-19: I tried to improve some details. But I believe this is more or less all I can achieve with CSS only. Some other issues in the UI may to be addressed in the code, for example:
Since HTML provides SELECT elements it's not clear why not using them. There are also components like select2 which can improve the usability of SELECT - but the current implementation with using INPUT and some script to open a list when focusing the element seems not very robust. Update 2023-03-26: I added two rules to fix the missing margins for input elements which are used to select options from drop down lists. Update 2023-03-26: I now added a media query which will position the labels and input elements on top of each other if the display is less than 1280px wide. This way the contacts app is at least usable on mobile devices as well, eventhough the mobile layout still needs more attention. Update 2023-03-28: Another little fix for input elements which contain multi select tags. |
|
Closing as duplicate therefore |


Is your feature request related to a problem? Please describe.
The current layout of the contact app is not very efficient. A lot of space is wasted and some labels can't even be displayed completely because of this.
Example - this is the view when having the browser full screen using the equivalent of 1920*1080 (4K with 200% scaling):
As you can see the contact details use three quite narrow columns with a lot of space left and right in the view. This means that the labels "Zusätzliche Namen", "Erweiterte Adresse" and "Bundesland oder Region" are not displayed completely.
Another issue is the invisible "trash can" icon which appears when touching elements - sometimes it is not clear what exactly that icon applies to. In some cases it means to delete a field only but in other cases a whole block will be affected. However there is no visual indication what exactly will happen when clicking the icon and deleting something will also happen immediately without any confirmation.
Describe the solution you'd like
The layout could be improved in the following way:
Describe alternatives you've considered
Provide the option to use your own HTML template with placeholders for the elements.
Additional context
The layout of iCloud contacts may be a inspiration how to create a clean and simple layout - even though I would not exactly copy it, but the general way how this was done is much easier to use for many people:
The text was updated successfully, but these errors were encountered: