[Bug]: rich workspaces makes loading jumpy, which makes fast navigation impossible

[JMoVS]

⚠️ 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

When rich workspaces are activated, them loading in and then displaying the content makes the position of the folders slightly jump around between initial loading spinner and final loading. As that takes more than a second very often, this is very frustrating if someone wants to navigate the folders fast.

Steps to reproduce

1. Create some content in the Readme.md so that rich workspaces loads the content in
2. navigate to a folder that contains such a readme
3. While the content of the readme gets loaded in, observe that the placeholder area is of different size than the final area used to present the contents of the Readme

Expected behavior

Reserve and fix a static amount of area for rich workspaces so that there is no difference in the vertical position of folders between start of loading and finished loading of the readme

Installation method

None

Nextcloud Server version

26

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

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

[rubenferreira97]

I feel this is a significant deal-breaker for the user experience and causes many users, including myself, to click on folders by mistake (resulting in entering the wrong folder, going back, and then clicking on the wrong folder again because the content jumped once more 😒).

A user interface should not exhibit content jumping (https://css-tricks.com/content-jumping-avoid).

One solution, as @JMoVS suggested, is to ensure that asynchronously loading content maintains a static size. In this case, you could consider setting a fixed height for the rich workspace and making it scrollable or relocating the rich workspace away from the top.

[skjnldsv]

cc @juliushaertl

[juliusknorr]

We addressed this in nextcloud/text#4776 for the upcoming Nextcloud 28, where we have all information ready at initial rendering time to reserve space only when needed.