-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
File names truncated in table view #5529
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
Prevent this from being closed: The problem persists in version 1.7.1. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
Hi could you check in try and on 1.8-rc. We put a title attribute on the filenames to help them be more visible. Would that solve your issue? |
With |
OK yeah it looks like #6258 wasn't backported to v1.8 |
OK it's now backported to the 1.8 branch. |
Do the changes on https://try.gitea.io look ok for you? |
The problem still exists in 1.8.0 and 1.9.0+dev-193-g46373e765. See https://try.gitea.io/veita/gitea-issue-5529/src/branch/master/filenames Compare with https://github.com/veita/gitea-test/tree/master/filenames |
OK, now I see. But unfortunately we have many long file names with a common prefix in our repos. Given such a situation, I think it is a little bit cumbersome to perform a binary search hovering over the table to find the desired file. I would prefer a more suitable column width (as GitHub), or a configuration parameter to customize it. |
@veita Github is still not so long? |
Hmm, it should be possible to make the length settable - and perhaps make the thing horizontally scroll automatically ? The problem is that we're getting exponential increase in our settings and I suspect that making things scrollable by default will break things. So three options:
I think 2 and/or 3 may be the correct answers - I suspect that most of us when hit by a long filename will read the first 10-15 characters and then skip to the end and read backwards. |
This looks way better than before. The common convention for the headline of commit messages is a maximum lenght of 50 characters. With your suggestion 50 characters seem to be displayable without an ellipsis, which is good with respect to usability. |
The trouble is it looks worse on tables with not-so-long filenames. We really need some better styling here. I think what is wanted is:
If at least one commit is long and all filenames are short:
if commits are all short and at least one filename is long:
and I guess we want a long filename to override the commit? |
You're right. GitHub also tries to balance out file names and commit comments. https://github.com/veita/gitea-test/tree/master/filenames |
This could probably be achieved using flex layout or table columns |
|
[x]
):Description
File names are being truncated in tabular views. Since we have several repositories with many files with common prefixes it is impossible to select the desired file e.g. from the project main page.
On the other hand, there's more than enough space left for the commit messages. Given, that by common convention, the commit message headline is limited to 50 characters this should usually be the case. So a solution could be to make file name columns wider and decrease the width of commit headline columns. Ideally these could be configuration parameters.
Screenshots
The text was updated successfully, but these errors were encountered: