arjitmalviya89 opened a new issue, #44415:
URL: https://github.com/apache/superset/issues/44415
### Bug description
### Bug description
On a multi-tab dashboard with native filters, applying a filter while on
one tab and then switching to the tab containing the charts leaves some
charts blank.
The data is NOT missing. In DevTools the chart's query response has
already arrived successfully with data. The chart simply never paints it.
Force refreshing the individual chart (ellipsis menu) renders the exact
same data correctly, confirming the response was valid all along.
Applying the same filter while already on the chart's own tab works
perfectly. The bug only occurs when the filter is applied from a
different tab.
Notably, on the same tab some charts render fine while others stay blank.
This appears to be a regression of #10349, which was fixed by #10432,
and was reported again against 5.0.0 in #36791 (closed as not planned
for lack of information).
### Screenshots
[apna screenshot yahan attach karo]
### How to reproduce
1. Create a dashboard with multiple tabs
2. Add a native filter (e.g. Year) scoped to charts on a different tab
3. Open a tab that does NOT contain the charts
4. Select a filter value and click Apply filters
5. Switch to the tab containing the charts
6. Table chart render blank
7. Force refresh an affected chart from its ellipsis menu - it renders
correctly with the same data
### Expected results
Charts should render with the filtered data when the tab becomes visible.
### Actual results
Charts remain blank despite their query response having already been
received successfully.
### Environment
- Superset version: 6.0.0
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution
- [x] I have searched the GitHub issue tracker and didn't find a similar bug
- [x] I have checked the logs and issue persists
<img width="1826" height="834" alt="Image"
src="https://github.com/user-attachments/assets/1d1b3c1f-abb8-4c47-b04a-dd2b33894f96";
/>
### Screenshots/recordings
_No response_
### Superset version
6.0.0
### Python version
3.11
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [ ] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
