MAIDR JavaScript API
    Preparing search index...
    • Line selectors: one per series of a line, step, area or precision-recall layer, naming the marks plotly drew for that series' trace.

      LineTrace pairs selector i with series i, so each trace is named by its own uid (scatterTraceScope); the group order inside .scatterlayer is the fill order, not the trace order.

      The marks are the trace's markers, one .point per sample, when every trace of the layer draws them. Otherwise they are each trace's line: plotly draws mode: 'lines' — the default way to draw a line or an area — as a path.js-line per unbroken run of samples, with no element per sample, and LineTrace puts a marker on each sample along it. A layer is read one way or the other, never some series by markers and the rest by lines: LineTrace resolves markers for the whole layer as soon as one series has them, and a series it then finds none for is left unhighlighted. A trace that draws no line has an empty path.js-line, so only its own series goes unhighlighted.

      A scattergl trace is painted to a canvas and has no element to name, and a uid that is not a usable class name names nothing either; both withdraw the whole list, since a list missing one entry pairs every series after it with the wrong trace.

      So does a line drawn as a staircase whose risers stand midway between the samples (hvh, vhv), when it is read off its path. Plotly draws the step between two samples of one value there as a riser of no height, which the step model reads as part of the run beside it, so it finds fewer steps than samples and marks each sample at a neighbour's place. No highlight is drawn rather than that one.

      Parameters

      • traces: readonly PlotlyTrace[]

        The layer's traces, one per series, in series order

      Returns string[] | undefined

      One selector per trace, or undefined when one cannot be named