Native Filters state breaks after clearing and "Apply filters" button remains disabled (Table charts)

[hugo10879]

Description

I am encountering a state management issue with Native Filters on a dashboard containing Table charts

When updating the filter values, the "Apply filters" button does not activate (it remains grayed out). Furthermore, after clicking "Clear all", the filters visually reset, but selecting new values in the filter fields completely fails to update the underlying state. The new selections are ignored, and the "Apply filters" button remains permanently disabled

Steps to reproduce

1. Open a dashboard containing Table charts with Native Filters enabled
2. Select or change values in the filter sidebar
3. Observe that the "Apply filters" button stays disabled despite valid inputs
4. Click "Clear all"
5. Try to select new filter values
6. Observe that newly selected values are not taken into account, and the "Apply filters" button remains unresponsive

Expected behavior

• Modifying any filter value should instantly activate the "Apply filters" button
• Clicking "Clear all" should reset the inputs, and any subsequent selection should register correctly, enabling the user to apply the new filters

Environment

• Apache Superset version: [6.1.0]
• Browser: [Firefox]

[dosubot[bot]]

Hi @hugo10879! I'm Dosu and I'm helping the Apache Superset team.

This behavior matches several filter state management bugs that have been fixed on master but likely haven't been cherry-picked into the 6.1.x release branch yet (a similar situation exists for other 6.1 filter bugs). Here's what's relevant to your report:

"Apply filters" button not activating when selecting filter values

PR #40470 (merged June 2026) fixed a regression in checkIsApplyDisabled where an early-return compared the count of selected vs. applied filters. This incorrectly disabled Apply whenever the selected state had an entry that the applied state lacked — exactly what happens when a user picks a value in a filter whose default never populated the applied state.

PR #38479 (merged March 2026) fixed a related issue where required filters with "Select first filter value by default" enabled would cause the Apply button to incorrectly disable when other filters were changed, due to a state synchronization gap during auto-apply.

"Apply" permanently disabled after "Clear All"

PR #39778 (merged May 2026) fixed handleClearAll dispatching cleared values directly to Redux instead of staging them, which broke the stage→apply UX and could push required filters into an invalid state.

PR #42111 (merged July 2026) addressed a further issue where "Clear All" staged the cleared value as undefined, which the select filter plugin treated as "uninitialized" — causing it to immediately re-apply defaults and leave Apply disabled. The fix stages null explicitly so the plugin treats it as intentionally empty.

What you can do: These fixes are all on master but don't appear to be in the 6.1.0 release. Upgrading to a build that includes them (or building from the latest master) should resolve the issues you're seeing. You may also want to watch the 6.1 release branch for cherry-picks.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.