[Bug]: Teams interface in Contacts papercuts
Open
Nobody has claimed this yet.
0. Needs triage
32-feedback
bug
feature: contacts
feature: teams
papercut
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
Content
- Almost no padding to the top, very squished
- Team avatar is strangely aligned, should be on top
- Links in descriptions not clickable
- Folder and collective filetype icons are too small
- File previews should be rounded rectangles, like in Files
- Talk conversation avatars should be circles, like in Talk
- Member list is horizontally cut off and has a scroll bar
- The content is limited in width more than it needs to, I think as also reported by @danxuliu
Left navigation
- Menu icon (3 dots) is black even in dark mode
- "Copy link" icon in action menu is black even in dark mode
- Teams info text should be color-text-maxcontrast
- Teams info text is not aligned with either the list entries nor the headings. Should probably be aligned with the headings (start a bit further left) as it’s a lot of text.
FYI @sorbaugh @kra-mo
Steps to reproduce
- Open Contacts
- Open a team
Expected behavior
See fix suggestions in the above section.
Nextcloud Server version
32
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by opening Contacts and then a team, following the listed reproduction steps. Review the content and left-navigation items against the referenced Files and Talk interfaces; done means the reported alignment, spacing, icon, link, sizing, color, scrolling, and width issues are addressed.
Written by the indexing model from the issue text.
Assessment
- Domain
- design, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100