[FEATURE]: Add `plotly_heatmapclick` event (similar to `plotly_treemapclick` / `plotly_sunburstclick`)
@nojaf ci sta già lavorando.
Dal 14/1/2026.
- Lingua principale
- JavaScript
- Stelle
- 18.3k
- Fork
- 2k
- Merge medio
- 2g 12h
- PR unite (30g)
- 28
Descrizione
Description
When using dragmode: "select", heatmaps do not fire plotly_click events for single clicks. This makes it impossible to handle both cell selection (drag) and single cell clicks in the same chart.
Treemap and Sunburst charts have dedicated click events (plotly_treemapclick, plotly_sunburstclick) that fire regardless of dragmode, but heatmaps have no equivalent.
Current Behavior
// With dragmode: "select"
graphDiv.on('plotly_click', (data) => {
// Never fires for heatmaps
});
graphDiv.on('plotly_selected', (data) => {
// Fires with undefined data on single clicks
});
Requested Behavior
Add a plotly_heatmapclick event (similar to how plotly_treemapclick works) that fires when clicking on a heatmap cell, regardless of dragmode setting.
graphDiv.on('plotly_heatmapclick', (data) => {
// data.points[0] contains { x, y, z, pointIndex, curveNumber, ... }
});
Why should this feature be added?
We're building reactive heatmap charts in marimo where users can:
- Drag to select a range of cells → works via
plotly_selected - Click a single cell to select it → does not work with
dragmode: "select"
Currently, users must drag even for single-cell selections, which is unintuitive.
Notes
If this feature is something the team would accept, I'm happy to submit a PR implementing it. Any pointers on where to start in the codebase would be appreciated (e.g., how plotly_treemapclick is implemented).
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Valutazione
Questa issue non è ancora stata valutata.