Multipage App + Background Callback Changes the Page
Open
Nobody has claimed this yet.
bug
P3
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
Issue steps:
- Trigger a background callback on Page X
- Change page to Y
- The background callback on Page X finishes and changes the browser to Page X
Background callback finishing shouldn't change page unless a dcc.Location is in the output.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by reproducing the issue with a minimal multipage Dash app, a background callback on Page X, and navigation to Page Y; trace the background callback completion and dcc.Location handling. Done means completing the callback leaves the browser on Page Y unless dcc.Location is explicitly in the callback output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100