MAIDR JavaScript API
    Preparing search index...

    Class TreemapTrace

    Trace implementation for treemaps and any other hierarchy laid out as area.

    A treemap encodes a tree as nested rectangles whose area is a magnitude. Every other trace in MAIDR is a flat grid, and a tree read as one loses the only thing the chart is drawn to show: a list of thirty leaves says nothing about which three of them make up most of Europe.

    The tree navigates as a tree, on the arrow keys that already exist. Up returns to the parent, down enters the first child, left and right walk the siblings -- the file-manager interaction, which is the one a reader already has. No new command, no new keybinding: a node's address is (depth, index-at-that-depth), and MovableGraph already navigates an arbitrary graph over such addresses. Siblings are linked to each other and nothing else, so left and right stay inside one parent; a cousin is reached by going up, across and back down, which is what the tree structure means.

    This is a chart a non-visual reading can do better than a visual one. A sighted reader compares areas by eye and is poor at it -- that is the standing criticism of the form. A reader given the tree is told each node's exact share of its parent, which is the comparison the rectangles are drawn to support and the one the eye estimates worst.

    The hierarchy is declared as a path, never as a parent pointer. A path is acyclic by construction and cannot be orphaned: a node whose ancestors are named is placed, and there is no id to dangle. Producers all have it -- a d3.hierarchy walk yields it directly, and Plotly's labels/parents pair resolves to it -- and it is also the breadcrumb, so the reader is told where they are out of the same field that put them there.

    Interior nodes need not be declared. A layer that emits only its leaves -- which is what a treemap draws -- gets its interior nodes and their totals derived. A layer that declares them keeps the declared numbers, since a parent may carry mass of its own that no child accounts for, and a total that disagrees with the sum of its children is a fact about the data rather than an error to correct.

    Hierarchy (View Summary)

    Index

    Constructors

    Properties

    observers: Observer<TraceState>[]
    isWarning: boolean
    isComputingStateAt: boolean

    True while AbstractTrace.getStateAt computes state at a temporarily moved cursor. Enforces (structurally, not just by documentation) that state getters never notify observers.

    id: string
    type: TraceType
    title: string
    name: string | undefined

    What this layer is, when the producer named it. See MaidrLayer.name.

    layer: MaidrLayer
    supportsExtrema: true

    ] and [ go to the largest and the smallest leaf, and the Go To dialog lists them: see TreemapTrace.getExtremaTargets. A tree whose nodes carry no magnitudes offers none.

    Unrelated to moveToExtreme, the Ctrl+arrow jump out to the branch root or in to the deepest descendant: that runs through the movable.

    movable: MovableGraph
    highlightValues: SVGElement[][] | null

    highlightValues[row][col], or null for the whole trace when it highlights nothing.

    A single cell may also be null, meaning the chart drew no element there. That is a narrower claim than the trace-wide null: the rest of the grid still highlights, and only this position falls back to the out-of-bounds state. A Google Charts calendar is the case it exists for -- its first and last columns are ragged, so a handful of grid positions have no rect at all while every other day does (#1174).

    Accessors

    • get isInitialEntry(): boolean

      Returns boolean

    • set isInitialEntry(value: boolean): void

      Parameters

      • value: boolean

      Returns void

    • get row(): number

      Returns number

    • set row(value: number): void

      Parameters

      • value: number

      Returns void

    • get col(): number

      Returns number

    • set col(value: number): void

      Parameters

      • value: number

      Returns void

    • get categoriesRunDown(): boolean

      Whether this trace's grid lists its categories as columns while the chart draws them one above another: a horizontal bar, dot, lollipop, funnel, dumbbell or forest chart. Its arrow keys are then turned to follow the drawing (keyDirection), as a horizontal box plot's already were: Up and Down move between the categories, and Left and Right along one, between the series, ends or sections drawn across it.

      Returns boolean

      False here; true on the traces of that shape drawn on their side

    • get xAxis(): string

      The x axis's name, falling back to a generic one the layer authored none.

      A getter rather than a field set in the constructor: the fallback is a translated word, and a trace outlives a language change — a name resolved once at construction would keep the language the chart was built in.

      Returns string

    • get yAxis(): string

      The y axis's name, or a generic one. See xAxis.

      Returns string

    • get z(): string

      The z axis's name, or a generic one. See xAxis.

      Returns string

    • get isEmptyAtCursor(): boolean

      Whether the cursor has no point to report.

      Read from dimension rather than from any one trace's data, because that is the one shape every trace already answers in. It is also evaluated at the cursor — LineTrace returns the current series' length as cols — so this covers a ragged layer, where one series has points and another has none, and not only a layer that is empty throughout.

      Returns boolean

      True when there is nothing at (row, col) to describe

    • get hasMultiPoints(): boolean

      Returns boolean

    • get layerLabel(): string

      How this layer names itself in the description dialog's layer tabs.

      The producer's name when there is one, and the chart-type label otherwise — the same fallback order TextService.layerIdentity uses for the spoken layer-switch announcement, so a tab and the announcement single out the same layer by the same name. The two differ only in register: the announcement says "point plot" where the dialog says "Scatter Plot", because that written form is what the dialog's own Chart Type line has always shown and a tab sitting above it should agree with it.

      Returns string

    • get placeAxisLabel(): string

      Returns string

      Trace.placeAxisLabel

    • get guide(): ChartGuide | undefined

      A plain-language introduction to this layer's chart type, for the description dialog. See chartGuide.

      A layer that names its own chart type never gets the trace type's: that guide explains the type the chart is read as, which is not what the chart is, and a gantt's tasks, dates and project plans said of a packet's bit fields are false. It gets the guide to the diagram it names (MaidrLayer.diagramType), or the one it gives to its own chart (MaidrLayer.typeGuide), or none.

      Returns ChartGuide | undefined

    • get orientationLabel(): string | undefined

      Which way this chart is drawn, or undefined for a type that has no orientation to speak of.

      Entering the chart already announces it -- "This is a maidr plot of type: horizontal bar" -- but the description dialog said only "Chart Type: Bar Chart", and for the box, violin and boxen families the orientation also silently reverses the order of the rows in the table underneath, because their constructors reverse the groups when the chart is horizontal. A reader comparing the table with what they walked had no way to know why the two disagreed.

      Exposed here, and read once by the description service, rather than pushed as a stat by each of the thirty-odd traces that has one. Named apart from the bar and distribution families' own orientation fields, which hold the declared* value and default it to vertical for every type -- including the ones that have no orientation at all.

      Returns string | undefined

      horizontal or vertical, or undefined when the type has no orientation to report.

    • get valueSpan(): number

      How far the layer's measured values spread: its largest less its smallest, or 0 with fewer than two. The scale at which [, ] and the Go To dialog read two values as one extreme (MathUtil.nearlyEqualInRange).

      Read from values, the numbers the layer is sounded and brailled from; a trace whose extrema rank something else says so by overriding it.

      Returns number

      The span, never negative

    • get traceType(): TraceType

      The trace's chart type. Lightweight alternative to reading state.traceType, which eagerly computes the full audio/braille/text/ highlight state just to expose this one string.

      Returns TraceType

    • get level(): "trace"

      Returns "trace"

      Trace.level

    • get state(): TraceState

      The state, with where the node sits among the siblings the arrows walk.

      The pan and the braille grid both run across a whole depth -- every node at it, whoever its parent -- so a position read from either said a lone card in a kanban's second column was "column 3 of 4", where left and right said there was nothing beside it.

      Returns TraceState

      The trace state

    • get values(): number[][]

      Returns number[][]

    • get outOfBoundsState(): TraceEmptyState

      The boundary tone sounds where the node the reader stopped at sounds: at the edge of its siblings on a treemap or a pack, at its angle on a sunburst. The base pans it by the node's index across the whole level.

      Returns TraceEmptyState

      The empty trace state, panned to the cursor's node

    • get highlight(): HighlightState

      On a node the layer derived from its children's paths, the nodes below it that the chart drew.

      A derived node was never declared, so no selector names it, and its own cell is a hidden placeholder: on a layer that lists only its leaves, the top level of the tree -- where the reader enters -- outlined nothing at all. What the chart draws of such a node is the block of its descendants, so they are outlined instead, as a closed scope of a directed graph outlines its members. A declared node outlines its own shape, as before.

      Returns HighlightState

      The highlight at the cursor

    Methods

    • Runs action with this element's observers muted.

      A cursor move normally is the announcement -- moveToIndex notifies, and everything downstream of it speaks, brailles and highlights. That is wrong for a move the reader did not make and is not waiting to hear: the description dialog's layer tabs relocate the reader in the chart while the modal is open, and the trace's announcement would land in the same live region the dialog is using, so one of the two is dropped. The caller announces afterwards, once, when the reader is back on the chart.

      Nesting is safe and the flag is restored on every path, including a throw, because a flag left raised would silence the chart for good.

      Parameters

      • action: () => void

        The moves to make in silence

      Returns void

    • Gets safe row and column indices to prevent accessing undefined values

      Returns { row: number; col: number }

      Object with safe row and column indices

    • The rotor's LOWER and HIGHER VALUE search. The base is a no-op that reports the boundary: a trace that can compare overrides it, and supportsCompareMode offers the two modes exactly where it does.

      Parameters

      • _direction: "left" | "right" | "up" | "down"
      • _type: "lower" | "higher"

      Returns boolean

    • Parameters

      • a: number

        Utility function to compare point values for rotor functionality

      • b: number
      • type: "lower" | "higher"

      Returns boolean

      boolean value

    • Rotor compare search along one row of numeric values.

      Steps from the current column in the given direction and moves to the first value that satisfies the comparison; reports the rotor boundary when nothing further qualifies. For the traces whose values are a plain numeric grid indexed [row][col]; a trace with a richer layout (the bar's orientation-normalised rows, the candlestick's segments) keeps its own.

      Parameters

      • rowValues: readonly number[]

        The values of the row being searched

      • direction: "left" | "right"

        Which way to search

      • type: "lower" | "higher"

        Whether a lower or a higher value is sought

      Returns boolean

      True when a matching value was found and moved to

    • Whether the rotor offers its lower and higher value modes on this trace.

      Exactly when the trace overrides moveToNextCompareValue. The base search is a no-op that reports a boundary, so offering the modes without one told a reader "No lower value found" with a lower value beside them, or said nothing at all; tying the offer to the search keeps the two from drifting apart again. A subclass can still override this to withhold the modes (scatter, whose arrows walk points rather than values), and a trace that compares only through the rotor's arrow methods must override it to offer them.

      Returns boolean

    • Returns the display name for the default data navigation mode. Override to provide a trace-specific name (e.g., "ROW AND COLUMN NAVIGATION" for scatter).

      Returns string

    • The rotor's lower and higher value search, Up: on a chart drawn on its side, along the categories toward the one drawn above, as Up moves. Elsewhere the rotor reads Up as Right.

      Parameters

      • Optionalmode: "lower" | "higher"

        Whether a lower or a higher value is sought

      Returns boolean

      Whether the cursor moved

    • The rotor's search, Down: toward the category drawn below. See moveUpRotor.

      Parameters

      • Optionalmode: "lower" | "higher"

        Whether a lower or a higher value is sought

      Returns boolean

      Whether the cursor moved

    • The rotor, Left: on a chart drawn on its side, the plain move along the category, as a horizontal box plot's rotor moves along its box. The search runs along the categories, which Up and Down walk there.

      Parameters

      • Optionalmode: "lower" | "higher"

        Whether a lower or a higher value is sought

      Returns boolean

      Whether the cursor moved. False at the end of the category -- on a chart of one series, always -- so the rotor says there is nothing further that way; it reported true, and the rotor said nothing.

    • The rotor, Right. See moveLeftRotor.

      Parameters

      • Optionalmode: "lower" | "higher"

        Whether a lower or a higher value is sought

      Returns boolean

      Whether the cursor moved, false at the end of the category

    • The direction to move the grid for a key, which is the key's own except on a trace whose categories run down the page. There the grid's columns are drawn one above another and its rows across them, so Up and Down step the columns, toward the category drawn above or below, and Right and Left step the rows. On a horizontal bar chart Right and Left moved down and up the page between the bars, and Up and Down said there was no more data: the other way round from a horizontal box plot or violin.

      Parameters

      Returns MovableDirection

      The direction to move the grid in

    • Whether the first category is drawn above the last.

      Producers list a horizontal chart's categories both ways: matplotlib, ggplot2, base R and Plotly draw the first at the bottom, and Highcharts, ApexCharts, Vega-Lite, seaborn and most hand-drawn charts at the top. So it is measured, as a Gantt chart measures its lanes, from the marks the highlight holds: in the first row that has two, the first category's mark is above the last one's, or below it. Measured on every vertical key, an autoplay step included, rather than once. That is two boxes a key, however many categories the chart has: the two marks are found from the ends of the row, and the read forces at most the layout the highlight's move would cause before the next paint. An answer kept from the first key was kept from a chart not yet laid out, or one since re-rendered the other way round, and a cache would have to be cleared on every redraw and resize to avoid that.

      Where nothing can be measured now, the last measurement holds, so a chart hidden for a moment does not turn the keys round under the reader. Where nothing has ever been measured -- a chart drawn to a canvas, one with no highlight, one not laid out yet, or one category -- the layer's MaidrLayer.firstCategory says where the first is drawn. Without it, the first is taken to be at the bottom, as row 0 of a grid is, and Up moves to the next.

      Returns boolean

      True when the first category is drawn at the top

    • The format the layer's author declared for an axis, or null when they declared none.

      For a number the description states rather than tabulates. The table reads each column through the axis's declared format, and so does every announcement, but a stat printed the raw number: a margin drawn as a percentage was "Min value: 0.12" over a table and a cursor saying 12%. Null rather than the default format when nothing was declared, so a chart nobody formatted reads as it did, which is the rule the table follows.

      Taken from FormatUtil.axisFormat, as the announcements and the table take theirs, so a histogram's bin edges read with the same decimals in all three.

      Parameters

      • axis: AxisType

        The axis whose format to read

      Returns FormatFunction | null

      The format, or null when the layer declared none

    • Cleans up trace resources including values and highlighted SVG elements.

      Only removes elements MAIDR created (hidden clones, synthetic markers); traces that highlight the chart's original live elements in place (e.g. heatmap cells, line dots) merely drop their references so the visible chart geometry survives focusout and live-data rebuilds.

      Returns void

    • Get all highlight SVG elements for this trace Used by HighlightService for high contrast mode

      Returns SVGElement[]

      Array of all SVG elements, or empty array if none

    • The chart's own element a marker this trace drew stands for, where the trace marks a point with a dot of its own rather than with a copy of the mark. None by default.

      Parameters

      • _marker: SVGElement

        A marker in this trace's highlight values

      Returns SVGElement | null

      The element the marker stands for, or null

    • Get all original (visible) SVG elements for this trace. These are the actual rendered elements, not the hidden clones used for highlighting. Used by HighlightService for high contrast mode color changes.

      Returns SVGElement[]

      Array of all original SVG elements, or empty array if none

    • Computes the trace state at an arbitrary position without moving the user's cursor or notifying observers. Used by monitor mode to sonify and announce a newly appended point while the user stays put.

      The state getters read this.row/this.col internally, so the cursor is moved temporarily and always restored in a finally block — this method is the single owner of that pattern.

      Re-entrancy hazard: this is only safe because the entire call chain is synchronous (no await points), so timers (e.g. autoplay ticks) cannot interleave before the finally-restore, and state getters never notify observers. If a getter ever becomes async or triggers notifications, callers could observe the temporary cursor.

      Parameters

      • row: number

        The row of the position to compute state for

      • col: number

        The column of the position to compute state for

      Returns TraceState

      The trace state at the requested position

    • Returns a human-readable label for this trace's chart type (e.g., 'Bar Chart', 'Scatter Plot') for display in the description modal. Falls back to the raw layer type if no mapping is registered.

      Returns string

    • What the entry instruction calls this chart: the name the layer gives its own chart type (MaidrLayer.diagramType or MaidrLayer.typeLabel), or the trace's word.

      A trace that names itself -- a line "single line" or "multiline", a radar "polar area" -- passes its word through here, so a layer that names its chart type is called by that name whichever trace reads it, and the instruction a reader hears once in the chart says what the one built from the layer before it said.

      Parameters

      • own: string

        The trace's word for its type

      Returns string

      The word the instruction uses

    • Builds the axes object for the description state, carrying only the axes the layer actually authored a label for. Subclasses should call this instead of constructing the axes object inline so charts without a real z dimension don't surface the placeholder default.

      Every axis is gated, not just z. xAxis and yAxis fall back to the literal 'X' and 'Y' when the JSON authors no label -- legal, and common in adapter-generated specs -- and the dialog rendered that as "X: X", a line that says nothing twice. The figure-level branch of the description already showed only authored labels (DescriptionService.getFigureAxes), so gating here is what makes the two levels of the same dialog follow one rule.

      Blankness is tested with trim(), the same rule named applies when it decides whether to substitute the fallback in the first place. A whitespace-only z label is truthy but blank, so the untrimmed guard used to pass it through and then print the 'Level' placeholder the guard existed to keep out.

      Returns { x?: string; y?: string; z?: string }

    • Whether the cursor stands on an extremum target, for a trace whose cursor its row and column do not hold: a scatter plot in point navigation keeps a point's index instead. Null leaves the answer to the row and column, which is how every other trace's cursor is read.

      Parameters

      Returns boolean | null

      True or false where the trace keeps its cursor elsewhere, and otherwise null

    • Returns true if this trace supports intersection navigation mode. Opt-in per trace type: override to return true (possibly conditionally, e.g. based on data shape) for trace types that expose point intersections between series. Intersection navigation is a trace-level capability — it has no meaning at the figure or subplot level, which is why it lives on AbstractTrace rather than AbstractPlot.

      Returns boolean

    • Returns true if this trace supports point-by-point navigation mode. Opt-in per trace type: override to return true for traces that expose individual data points navigable in reading order (left/right) and column-major order (up/down). Currently only ScatterTrace.

      Returns boolean

    • Notifies the trace that the rotor is entering or leaving INTERSECTION_MODE. Default is a no-op; line-style traces don't need to track mode state because their state output is unchanged by the rotor mode. Traces whose audio/text output differs in intersection mode (e.g. ScatterTrace, which normally plays the whole x-column as a chord and must instead focus a single point) override this to flip an internal flag.

      Parameters

      • _enabled: boolean

        True when entering intersection mode, false when leaving.

      Returns void

    • Moves to the object the list knows by this key, announcing it through the usual observer chain.

      Looks the key up in a list built now rather than trusting a cell the dialog was handed when it opened, so a chart whose data changed under the dialog moves the reader to the object they chose or nowhere at all.

      Parameters

      • key: string

        The key the object list gave the object

      Returns boolean

      True when the cursor moved, false when no object has the key or its cell cannot be reached

    • How this layer's x axis writes an x: through the format the layer declares for it, or null where it declares none.

      A layer switch carries a number this way to a layer that holds the same place as text (see Subplot.carriedXValue).

      Parameters

      • xValue: XValue

        An x of this layer's

      Returns string | null

      Its reading, or null

    • The x of this layer's that its axis writes as reading: the first in the order the points are held, or null where the layer declares no x format or none of its x reads that way.

      A layer switch carries text this way to a layer that holds the same place as a number its axis formats (see Subplot.carriedXValue).

      Parameters

      • reading: string

        The text another layer holds the place as

      Returns XValue | null

      The x, or null

    • Moves the active point to the pointer location and returns directional guidance toward the nearest data geometry in a single call.

      Combining both operations avoids running findNearestPoint twice per pointermove event — important on dense plots where the scan is the hot path.

      Parameters

      • x: number

        Screen-space x position of the pointer/finger

      • y: number

        Screen-space y position of the pointer/finger

      Returns PointerGuidanceState | null

      Guidance state relative to nearest point, or null when unavailable

    • Moves the trace to the nearest point when the pointer is within its bounds and the trace is not already focused on that point.

      onCurve is intentionally non-optional: the caller has already paid the cost of isPointInBounds to assemble guidance state, and forcing subclasses to accept the value makes the contract explicit so a future override cannot silently recompute (or worse, ignore) it.

      Subclasses override this to customise hover-driven navigation:

      • Box / ViolinBox no-op the move while still surfacing guidance.
      • Scatter switches into column navigation mode before delegating.

      Parameters

      Returns void

    • Checks if the specified coordinates are within bounds of the element.

      Parameters

      • x: number

        The x-coordinate

      • y: number

        The y-coordinate

      • element: NearestPoint

        Object containing the SVG element and its position

        • element: SVGElement
        • row: number
        • col: number
        • centerX: number
        • centerY: number

      Returns boolean

      True if the point is in bounds, false otherwise

    • The node's name, which is what another layer of the same chart can find it by. The default read a magnitude or nothing, so a layer switch landed a reader on whatever came first rather than on the same node.

      Returns XValue | null

      The name of the node under the cursor, or null off the chart

    • Whether a mark of this trace sits at exactly this X, as moveToXValue finds one before it falls back to the nearest.

      A layer switch asks this to choose between the two X values a position can offer (see Trace.getAlternateXValue). Reads the x of each point; a trace that keeps its X some other way answers false unless it says otherwise, and the switch then carries what it always carried.

      Parameters

      • xValue: XValue

        The X a layer switch would carry

      Returns boolean

      True when some point's x is exactly xValue

    • Offers a walk along the whole level, across parents.

      The arrow keys stay the tree: left and right are siblings, and a step past the last child of a parent is refused rather than landing in a cousin's subtree unannounced. That is the right default and it is what makes this a hierarchy rather than a grid -- but it is not the only reading anyone wants. An icicle is drawn as depth-ordered bands, a whole row of blocks per level, and "everything at this depth, in layout order" is a question that reading asks directly.

      So the band goes on the rotor rather than on the arrows. One data model with two different arrow semantics, chosen by which layout the producer happened to pick, would be worse for a reader who meets both than one semantics plus an explicit mode.

      Withheld on a level of one, where it could only ever answer "none found".

      Returns readonly RotorFilterUnit[]

      The level unit alongside whatever else is offered

    • Moves within an active rotor filter unit along the filtered axis.

      Called by RotorNavigationService when the current rotor mode is one of this trace's getRotorFilterUnits. Filter units navigate a single axis, so only left/right are dispatched here — the service announces up/down as unavailable without calling the model (matching intersection mode). Implementations should move to the nearest point matching the unit identified by key and notify observers, returning true; when no such point exists they should call notifyRotorBounds and return false.

      Default is a no-op that reports bounds, so a trace advertising a filter unit but forgetting to implement movement fails safe (announces "no point found") rather than moving unexpectedly.

      Parameters

      • key: string
      • direction: "left" | "right"

      Returns boolean

      True if the cursor moved, false otherwise

    • Jumps to an extreme of what the arrow keys walk.

      On the Level unit, Left and Right walk the whole level across parents, so Control with them goes to the first or last node of the level, and is refused only there. It went to the ends of the node's siblings instead: on a timeline's last period of a section, Control+Right said there was no more data while Right went on to the next section's first period. Up and down, and every jump off the Level unit, keep the tree's own extremes.

      Parameters

      Returns boolean

      True when the cursor moved, or entered the tree

    • Why [, ] and G have nothing to go to on a tree drawn without values, such as an org chart: its nodes have no magnitude to rank.

      Returns string | null

      That the nodes carry no values, or null on a valued tree

    • Every node of the tree, as the o list offers them.

      Listed as an outline -- each parent before its children, siblings in the order they were declared -- because that is the order a tree view shows and the one in which a node's path is already known by the time the reader meets it. The address the cursor walks is by depth, which would list every continent before any country and leave the countries cut off from the continent they belong to.

      The sorts are the comparisons the rectangles are drawn for: the largest nodes first, or on a tree with no magnitudes -- an org chart -- the largest teams. The filters are the tree's own levels, and, once the reader is on a node with anything below it, everything inside that node: with "Value, highest first" that is "the largest countries in Europe", which the arrow keys answer only by walking every sibling.

      Returns ChartObjectList | null

      The list, or null when the tree has no nodes

    • The largest and the smallest leaves, for ], [ and the Go To dialog.

      Leaves rather than every node: a branch's magnitude is its children's total, so the largest node would always be a top-level one, and the description names the largest leaf and the range of the leaves. Each is named by its path, as the description names it, so two leaves called alike under different branches are told apart. Every leaf holding an extreme is offered, level by level, so a tie is walked. A tree whose nodes carry no magnitudes has nothing to rank, and offers none.

      Returns ExtremaTarget[]

      The targets, or none for a tree without magnitudes