graceguo-supercat commented on pull request #14693:
URL: https://github.com/apache/superset/pull/14693#issuecomment-844269731


   > @junlincc Are you sure that tabs were getting highlighted? I don't see the 
relevant code and there are no tabs highlights in the gif from Grace's comment 
here [#10936 
(comment)](https://github.com/apache/superset/pull/10936#issuecomment-707224331)
   
   For filter_box, we don't highlight tabs when only charts inside inactive tab 
will be impacted. We had this behavior is because filter_box could be placed 
inside tab. So that if a filter_box only has smaller tab scope, it should be 
placed inside the tab. It is possible that user sets a filter_box is applicable 
to multiple tabs but hide the filter_box inside a nested tab, but this case is 
small (why would someone do that?)
   
   For build-in filter components, things are a little different: every filter 
component become globally visible in the dashboard, not matter it is applicable 
to single nested tab or multiple top-level tabs. This change might need us to 
think about the highlight behavior:
   
   - When a filter component is applicable to a nested tab and currently user 
can not see the nested tab, filter component should be inactive (not in the 
current implementation but i assume this is in the near future), i think we 
still should highlight the scope even for the inactive filter component, so 
that user will know why the filter is not active now and what is its real 
scope. We should highlight the parent tab which is visible for the user when 
the charts are deep nested under other tabs.
   
   - When a filter component is applicable to one more charts/tabs in the 
current active tab, filter component is active, we should highlight charts and 
tabs, so that behavior is consistent with above case.


-- 
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.

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