Greater than filter shouldn't remove NaN values

[mkfreeman]

It feels odd that adding a greater than filter removes NaN values (which we bin into the invalid number category).

I would expect the NaN values to still be visible after applying this (persistent filter):

no filter:

with filter: (notice yellow bar is missing, as are NaN values from the table rows)

[mbostock]

This seems like the desired behavior to me. Comparing anything with NaN is always false, so all undefined/null/NaN vales should be removed with any threshold comparison (>, <, >=, <=).

[1, 2, 3, 4, NaN].filter((x) => x > 2) // [3, 4]

[annie]

@mkfreeman do we still want to modify this behavior, or can we close this issue?