The chart container's id
Which series in the chart this is
How many rows the grid has
How many columns the grid has
Whether Highcharts already draws y index 0 at the top, meaning the adapter left the payload's rows as they were
The same question of the x axis: whether Highcharts already draws x index 0 at the left, meaning the adapter left each row's columns as they were (#1008)
selectors[r][c], indexed the way the model indexes its cells
Generates a 2D grid of per-cell CSS selectors for a Highcharts heatmap series.
MAIDR's
HeatmapTrace(when given astring[][]) treatsselectors[r][c]as the selector for the cell at logical rowr, columnc, having reversed the incoming rows so that row 0 is the bottom of the visual grid. The adapter stampsdata-maidr-rowwith Highcharts' own y index, so this walks the same path back: which stamped row is logical rowrdepends on whether the adapter turned the payload over on its way out.On an ordinary axis it did — Highcharts counts y from the bottom while the grammar runs top-first — and the two reversals cancel, leaving logical row
ron stamped rowr. On a reversed axis the payload passed through untouched, so only the model's reversal applies and the index has to be flipped (#973).Highcharts emits heatmap cells in
series.dataorder, which depends on the user's data layout (could be row-major or column-major). DOM-order based mapping is fragile across user configs; per-cell stamping (seestampHeatmapIndicesin adapter.ts) makes the selector→cell mapping unambiguous regardless of insertion order.