nigzak opened a new issue, #27623:
URL: https://github.com/apache/superset/issues/27623

   ### Bug description
   
   the crossfilter scoping is ignored after reloading the dashboard
   crossfilter is re-enabled after set scope and reloading the page
   
   ### How to reproduce the bug
   
   visit dashboard with two tabs
   1st tab has different dashboards
   2nd one has a raw table
   
   enable crossfilter
   enable scoping for only one tab (1st one)
   
   switch tabs => cross filter is only enabled for 1st one, it is disabled for 
2nd one
   switch to 2nd tab
   cross filter still disabled
   
   reload page (F5) => superset switch to 2nd tab
   switch to 2nd tab
   
   crossfilter is active
   check scoping => 2nd tab is INACTIVE - but crossfilter is still active
   
   (same for open it via navigate => dashboard)
   
   => superset only uses the scoping for crossfilter on the initial setup, 
after reload/re-visit it is ignored
   
   ### Screenshots/recordings
   
   
![image](https://github.com/apache/superset/assets/102737855/9d9cda35-6510-4e86-809c-82035c5bf5b7)
   
   
   ### Superset version
   
   3.0.4
   
   ### Python version
   
   3.9
   
   ### Node version
   
   I don't know
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [X] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [X] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [X] 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]

Reply via email to