Re: [I] [Bug] Cannot drag when yAxis min and max not set and first symbol dragged beyond the displayed value by ECharts [echarts]

["cschanhniem (via GitHub)" <gi...@apache.org>]

cschanhniem commented on issue #21663:
URL: https://github.com/apache/echarts/issues/21663#issuecomment-4917291917

   The drag misbehavior when min/max are unset has a plausible root cause in how the axis range is recalculated during the drag loop. When `yAxis.min` and `yAxis.max` are not explicitly set, ECharts derives them from the data extent with padding. During a drag operation, the dragged data point moves beyond the displayed value range, which triggers an axis extent recalculation that shifts the axis boundaries — moving the target that the gesture is tracking.
   
   This creates a feedback loop: drag beyond visible range → axis recalculates → the visual position of the point changes → the gesture picks up a new delta. The fix would likely involve either clamping the drag delta against the current axis domain or temporarily freezing axis extent recalculation for the duration of the drag gesture.
   
   Would be worth testing whether pinning `yAxis.min` and `yAxis.max` to fixed values (or using `min: 'dataMin'` / `max: 'dataMax'` explicitly) prevents the issue as a workaround.
   


-- 
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: commits-unsubscribe@echarts.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@echarts.apache.org
For additional commands, e-mail: commits-help@echarts.apache.org