Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Feature Request] Customizing Document Title Per Callback

Abierto
#3,782 3 comentarios 0 reacciones 1 asignado Ver en GitHub

@AnnMarieW ya está trabajando en esto.

Desde el 20/5/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

enhancement P3 size: 3

Hi, this is a great enhancement! I have a suggestion for further customization regarding the document title updates.

Could we allow specifying the update_title behavior on a per-callback basis?

My reasoning is that not all callbacks require the same title update strategy. The way I would divide callbacks is into two categories -

  1. User-triggered callbacks: For these (e.g., button clicks, form submissions), it would be very beneficial to set a dynamic title like update_title="Updating..." to provide immediate user feedback during processing.

  2. Automated/Background callbacks: For callbacks like dcc.Interval (which I use for periodic updates or access control checks), changing the document title would be distracting and unnecessary. For these, I'd ideally want to explicitly disable the title update, perhaps by setting update_title=None.

While I have seen suggestions on using clientside callbacks for this, I believe allowing this granular control within dash would significantly improve the user experience by enabling context-appropriate title changes without polluting the title bar for background operations and the developer experience by not expecting the developer to write a clientside callback for every relevant callback. Thanks!

Additional context
Old PR that allows global enable or disable of Document Title update and changing the text of the Document Title when updating #1343
Similar Issue but focuses more on Location and Tabs

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

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de plotly/dash

Todos los issues de plotly/dash

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.