[BUG] Loading disappears too soon when callback updating its content is triggered multiple times
@KoolADE85 ya está trabajando en esto.
Desde el 28/10/2025.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Describe your context
Please provide us your environment, so we can easily reproduce the issue.
- replace the result of
pip list | grep dashbelow
dash 3.2.0
dash_ag_grid 31.3.1
dash_auth 2.3.0
dash-bootstrap-components 2.0.4
dash-bootstrap-templates 2.1.0
dash-extensions 2.0.4
dash-iconify 0.1.2
-
if frontend related, tell us your Browser, Version and OS
- OS: iOS
- Browser chrome
- Version 141.0.7390.66 (Official Build) (arm64)
Describe the bug
I have a callback that updates a component inside a dcc.Loading. When this callback is triggered multiple times, the loading overlay disappears after any of them finishes, but data is updated only after the last one finishes.
This is quite problematic, as if a callback has multiple inputs, and user changes more than one in a quick succession, the loading overlay disappears before the data is updated, providing misleading information.
Expected behavior
Loading overlay disappears only after the last callback finishes and data is updated.
MWE
Click the button, wait a second or two, and click it again. Loading overlay disappears 3 seconds after the first button click, data appears 3 seconds after the second button click.
from time import sleep
from dash import Dash, Input, Output, callback, dcc, html
layout = [
html.Button("Button", id="button"),
dcc.Loading(html.Div(id="target")),
]
@callback(
Output("target", "children"),
Input("button", "n_clicks"),
prevent_initial_call=True,
)
def x(b):
sleep(3)
return b
app = Dash(__name__)
app.layout = layout
app.run()
- Lenguaje dominante
- Python
- Estrellas
- 24.4k
- Forks
- 2.3k
- Merge medio
- 1 d 21 h
- PR fusionados (30 d)
- 19
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de plotly/dash
-
good first issue P3 size: 1 task
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
enhancement P2 size: 5
Dificultad 5/5 Más de una semana Aptitud para principiantes 45/100
-
enhancement P3 size: 10+
-
P2 size: 1 task
-
enhancement P3 size: 1
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
Todos los issues de plotly/dash
Issues similares
-
essnmx good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
-
[Feature] 奇物选择添加优先级 Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
syfoud/Simulated_Scepter#174 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Giskard-AI/giskard-oss#2840 · 1 comentario ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Abiertoarea: repo bug perceived difficulty: 2
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
yeti-platform/yeti#1380 ·