Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature Request] Customizing Document Title Per Callback

Aperta
#3,782 3 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@AnnMarieW ci sta già lavorando.

Dal 20/5/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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

Lingua principale
Python
Stelle
24.4k
Fork
2.3k
Merge medio
1g 19h
PR unite (30g)
19

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di plotly/dash

Tutte le issue di plotly/dash

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.