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
If client-side JS fails, the new home page is a loading spinner, which runs forever.
The new About pages, which are rendered on the server, do show static content.
Screen.Recording.2024-09-27.at.11.07.36.mov
To Reproduce
Either disable JS, or block one of the home page bundles from loading, then visit the home page.
Alternatively, use dev tools to throttle your connection to a very slow speed.
Expected behavior
Static content, like the list of blog posts, should at least load, even if JS is required to log in and fetch recent projects, classifications, etc.
Additional context
Client-side JS will fail for ~1% of any site's visitors. I think I had a slide about this in one of my old Zoominar presentations. It's best practice to show some static HTML & CSS content, even when JS is disabled.
The text was updated successfully, but these errors were encountered:
Package
Describe the bug
If client-side JS fails, the new home page is a loading spinner, which runs forever.
The new About pages, which are rendered on the server, do show static content.
Screen.Recording.2024-09-27.at.11.07.36.mov
To Reproduce
Either disable JS, or block one of the home page bundles from loading, then visit the home page.
Alternatively, use dev tools to throttle your connection to a very slow speed.
Expected behavior
Static content, like the list of blog posts, should at least load, even if JS is required to log in and fetch recent projects, classifications, etc.
Additional context
Client-side JS will fail for ~1% of any site's visitors. I think I had a slide about this in one of my old Zoominar presentations. It's best practice to show some static HTML & CSS content, even when JS is disabled.
The text was updated successfully, but these errors were encountered: