Problem
The global keyword filter changes which rows are visible in the table, but column stats/totals still appear to be computed from the unfiltered dataset.
Current behaviour:
- Apply a global keyword filter.
- The table only shows rows matching the keyword.
- Column stats/totals still count hidden rows that no longer appear in the table.
If the UI is showing a filtered table, the visible column stats should describe the filtered/visible row set unless explicitly labeled otherwise.
Expected behaviour
Column counts, totals, stats, and rendered rows should all be derived from the same filtered row set.
Specifically:
- Global filter should be applied before column stats are computed.
- Column totals should only include rows currently visible after filtering.
- Column counts should never become negative. The cause of behaviour needs to be triaged and fixed.
- Totals should re-render correctly when filters are applied, changed, or cleared.
- Table rendering and column stats should not disagree about which rows are active.
If full-dataset stats are needed later, they should be shown separately and explicitly labeled, for example:
Filtered total
All rows total
Repro
In any frontend table:
- Apply global filter:
[keyword]
- Confirm only matching rows are visible.
- Inspect column stats/totals for any column, e.g.
Total.
- Actual: stats/totals still include hidden rows, or counts/totals render incorrectly.
- Expected: stats/totals only reflect the visible filtered rows.
Implementation notes
The fix is to make filtering and analysis operate from one canonical snapshot instead of allowing table rows, stats, and totals to derive from different state.
Problem
The global keyword filter changes which rows are visible in the table, but column stats/totals still appear to be computed from the unfiltered dataset.
Current behaviour:
If the UI is showing a filtered table, the visible column stats should describe the filtered/visible row set unless explicitly labeled otherwise.
Expected behaviour
Column counts, totals, stats, and rendered rows should all be derived from the same filtered row set.
Specifically:
If full-dataset stats are needed later, they should be shown separately and explicitly labeled, for example:
Filtered totalAll rows totalRepro
In any frontend table:
[keyword]Total.Implementation notes
The fix is to make filtering and analysis operate from one canonical snapshot instead of allowing table rows, stats, and totals to derive from different state.