You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When opening an asset folder on a slow connection, the loading indicator (spinning circle graphic) is often not visible if you have a long container. This is because the loading indicator is placed in the vertical middle of the container, which is often out of the viewport. As a result, you just see a transparent white background over the folders and files, and it appears that nothing is happening.
Steps to reproduce
Open an asset folder which has many assets on a slow connection
Expected behavior
The loading indicator should reside in the viewport regardless of how many assets are in the folder
Actual behavior
The loading indicator is out of the viewport, as in this screenshot:
Craft CMS version
4.4.X
PHP version
No response
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
The text was updated successfully, but these errors were encountered:
What happened?
Description
When opening an asset folder on a slow connection, the loading indicator (spinning circle graphic) is often not visible if you have a long container. This is because the loading indicator is placed in the vertical middle of the container, which is often out of the viewport. As a result, you just see a transparent white background over the folders and files, and it appears that nothing is happening.
Steps to reproduce
Expected behavior
The loading indicator should reside in the viewport regardless of how many assets are in the folder
Actual behavior
The loading indicator is out of the viewport, as in this screenshot:
Craft CMS version
4.4.X
PHP version
No response
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
The text was updated successfully, but these errors were encountered: