Marc-André Rivet

@interrogator Thanks for the feedback. This can currently be done through the conditional formatting, but you are right that it's neither as nice, performant, or flexible as real native heatmaps...

1.13.0 would be https://github.com/plotly/dash-core-components/commit/91a424e73d5b4592265175b35dada98dc6d88182

As for https://github.com/plotly/dash-table/issues/850 tagging is currently problematic as the Julia release requires the branches not to be version tagged. The last Julia release use https://github.com/plotly/Dash.jl/blob/dev/Project.toml#L25 so `>1.10.2` can't be tagged

Looks like the issue is specific to clearing / emptying the filter. Changing the filter for another valid / not empty one updates correctly.

Running this locally, the network call takes ~400ms and the dropdown rendering ~8.5 seconds with the 100k items example above. Most if not all the initialization time seems to be...

**Investigation results** So.. we are using `react-virtualized-select` for the dropdown rendering and `react-select-fast-filter-options` for the underlying search functionality. fast-filter is using `js-search` to index the available options. `js-search` creates a...

We actually had someone suggesting something similar (server-side updates to the dropdown options) [here](https://github.com/plotly/dash-core-components/issues/438). Turns out the react-virtualized-select component does not behave well when its options are changed on the...

Moving this issue to the dash-core-components repo.

The short answer to this one is `no` with the current implementation. The `relative` parent of that dropdown is inside the table component, which sits inside the "no-overflow" div container,...

@wbrgss 4.11.0 commit in master: https://github.com/plotly/dash-table/commit/aa519b79a6bc1783d98bf7b1fa0086853a484627