-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Not all subfolders are displayed depending on the scale of the page #1540
Comments
I can confirm this issue. It always happens for long lists of files/folders after scrolling a few pages. The scrollbar has the right length, so enough space is reserved, but the thumbnails are not displayed. Any action which changes the viewport size like zooming, resizing the browser or opening the developer sidebar causes the thumbnails to be loaded. |
Confirmed as well on firefox. resizing does effect which photos or folders are loaded, but it still wont display all of them at once for me. I just get a bunch of blank space before and after that never loads. I hope this one can get fixed soon |
Confirmed on firefox and on chrome. Zooming the page in or out reloads part of the page and thumbnails, but not all. |
Confirmed on firefox |
A fix for this was made in #1695 and backported as far back as v25.0.6. Can you confirm it is fixed in your environment? If so, please close this Issue! |
I can confirm the issue is fixed in 27.0.0. |
Thanks @joshtrichards ! |
Describe the bug
Not all subfolders are displayed depending on the scale of the page.
For example, in the folder "2021" we have 143 subfolders.
The Files app shows all 143 subfolders without issue.
In the Photos app, when you open the 2021 folder, only 77 subfolders are displayed (1920*1080 screen, 100% page zoom).
If you start zooming out of the page in the browser, then the missing folders will appear below.
To Reproduce
Steps to reproduce the behavior:
Screenshots
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The problem also occurs on other browsers, including mobile devices.
NC: 25.0.2-fpm
The text was updated successfully, but these errors were encountered: