[GH-ISSUE #71] Show skeleton instantly instead of the progress bar #46

Closed
opened 2026-03-03 10:56:23 +03:00 by kerem · 1 comment
Owner

Originally created by @manikanta9176 on GitHub (Apr 21, 2025).
Original GitHub issue: https://github.com/dflow-sh/dflow/issues/71

Originally assigned to: @manikanta9176 on GitHub.

  • When switching tabs, the page loads quickly and the skeleton appears while the data is being fetched.
  • However, when opening a server, the page takes longer to load. The progress bar is shown first, then after the page load, the skeleton appears, and finally the UI is rendered.
  • Ideally, the skeleton should be displayed immediately while the data is loading, instead of waiting for the full page load.
Originally created by @manikanta9176 on GitHub (Apr 21, 2025). Original GitHub issue: https://github.com/dflow-sh/dflow/issues/71 Originally assigned to: @manikanta9176 on GitHub. - When switching tabs, the page loads quickly and the skeleton appears while the data is being fetched. - However, when opening a server, the page takes longer to load. The progress bar is shown first, then after the page load, the skeleton appears, and finally the UI is rendered. - Ideally, the skeleton should be displayed immediately while the data is loading, instead of waiting for the full page load.
kerem 2026-03-03 10:56:23 +03:00
Author
Owner

@manikanta9176 commented on GitHub (Apr 21, 2025):

The issue with showing the skeleton instantly instead of the progress bar is primarily due to the layout. I attempted to implement changes using Suspense and the loading.tsx file, but this approach resulted in missing tab-level skeleton loading.

To resolve this, we may need to revisit the layout or adjust the routing structure by making each tab a separate page. This would allow for proper skeleton loading on each tab.

<!-- gh-comment-id:2818264326 --> @manikanta9176 commented on GitHub (Apr 21, 2025): The issue with showing the skeleton instantly instead of the progress bar is primarily due to the layout. I attempted to implement changes using Suspense and the loading.tsx file, but this approach resulted in missing tab-level skeleton loading. To resolve this, we may need to revisit the layout or adjust the routing structure by making each tab a separate page. This would allow for proper skeleton loading on each tab.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dflow#46
No description provided.