ShanteshSindgi commented on issue #21744: URL: https://github.com/apache/echarts/issues/21744#issuecomment-5709788548
Reopening this — the hoverLayerThreshold workaround from @helgasoft does restore legend-hover highlighting on the SVG renderer, but I'd like maintainer guidance before relying on it, since the docs don't fully describe this behavior. Questions: Is the underlying breakage a bug you intend to fix? Should legend hoverLink emphasis stay responsive regardless of point count without needing a hoverLayerThreshold override? If a fix is planned, we'd rather wait for it than hard-code a threshold. How should the threshold value be chosen? From updateHoverLayerStatus, the threshold is compared against the chart's total rendered element count (elCount), not just data points. So a fixed offset like dataCount + 45 under-counts on charts with extra axes/legend/toolbox/dataZoom, and the hover layer re-engages unexpectedly (re-breaking the highlight). Is there a recommended way to compute a safe value, or an intended fixed element-count value? Does the hover layer apply to the SVG renderer at all? The [docs](https://echarts.apache.org/en/option.html#hoverLayerThreshold) describe it purely as a canvas optimization ("avoid re-painting the whole canvas", "extra canvas", "burden on mobile devices"), yet in practice the threshold clearly affects SVG legend-hover highlighting. Is the hover layer meant to be active under SVG, or is the SVG breakage an unintended side effect? And on SVG, is keeping the hover layer off (high threshold) safe with no real memory/perf cost? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
