Hi Dash team,
We are currently doing a POC on Dash 4.0.0 RC and wanted to share some observations and get guidance before we move further
Loading icon behavior (main concern):
What we see right now:
-
dcc.Loadingworks fine when callbacks are triggered by user actions (Apply button, filter click, etc.) -
On initial page load:
Callbacks do execute (data loads correctly)
But loading spinner is not shown
User just sees blank graph / table for a few seconds
This was not the case in Dash 2.x. Earlier, users always saw a spinner during initial load.
What we did as a workaround: To avoid bad UX, we added a custom overlay spinner for initial page load and kept dcc.Loading for user-triggered actions.
This works functionally, but now:
- We have two different loading icons
One fromdcc.Loading
One custom overlay spinner - UI looks inconsistent
- Extra state + extra code to maintain
**Our understanding of the issue: **
From what we observed:
-
In Dash 4, loading detection works differently
-
On initial load:
Page renders
Callback fires almost immediately
dcc.Loadingdoesn’t reliably catch that execution -
Result → no spinner, even though callback is running
Just want to confirm:
**Is this expected behavior in Dash 4 or a known issue?
**
Questions we need help with :
-
Is the initial page load loading issue expected in Dash 4?
-
Will this be fixed in Dash 4 GA?
-
What is the recommended way to show loading indicators?
-
Should teams rely on custom overlays or wait for a native fix?
-
Apart from
dash-ag-grid>=32.0.0, is there anything else we must upgrade? -
How long should we expect this behavior to remain?
Regards,
Munish Singla