nextcloud / nextcloud/server

Number of files and size of folder are sometimes not easily accessible

Open
#33,261 16 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage design enhancement feature: files
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

Current situation

Currently, the files summary (number of directories and/or files, the directory size are shown at the end of the file list, like so:

image

Now, when viewing a folder in the files app where there are more files in the list, than can be displayed on the screen, this line is not visible until you scroll till the end of the list:

image

Why this is an issue

IMO, it is already non-user-friendly if a users just wants to know the number of items and she or he has to scroll to the bottom of the list.

But it becomes even more cumbersome, if one has loads of files and these files are loaded incrementally. And it's even worse, if its a list of pictures, where thumbnails are shown and the thumbnails have not been created yet. So you scroll down, get a glimpse of the information you are looking for (since the table footer is already there) but then it disappears again as the list is expanded, new thumbnails are loaded, slowing down the server, scrolling down again, ... You get the picture.

And all this, while the information you have been looking is there all along since the first page load. Just hidden from your eyes....

<tfoot>
  <tr class="summary">
    <td/>
    <td class="filesummary">
      <span class="info">
        <span class="dirinfo">1 folder</span>
        <span class="connector">and</span>
        <span class="fileinfo">6 files</span>
        <span class="hiddeninfo hidden">(including 0 hidden)</span>
        <span class="filter hidden"/>
      </span>
    </td>
    <td class="filesize">462 B</td>
    <td class="date"/>
  </tr>
</tfoot>

Possible solutions

  1. Move the row summary to the table head. That would be quick and easy and would, in my point of view, create the most consistent user experience, as the information is always at the top, at the same place, no matter if 0, 1, a few or many entries in the given directory.
  2. Keep it at the bottom, but do some CSS magic, that keeps the table footer always visible. But this gets messy very quickly, depending on the browser used by the user.

Files affected (to be completed)

Possibly related/affected issues:



Foot note as requested by NC's issue template

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with apps/files/templates/list.php around the table markup and apps/files/js/filesummary.js, then trace where the summary row is added to the table footer. Compare the proposed header placement with the existing footer behavior and related issue #28063. Done means the files and folder summary remains visible without scrolling, including while entries load incrementally.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.