lukas-sl opened a new issue #16746:
URL: https://github.com/apache/echarts/issues/16746


   ### Version
   
   5.3.1
   
   ### Link to Minimal Reproduction
   
   https://codesandbox.io/s/echarts-datazoom-bug-q196p9
   
   ### Steps to Reproduce
   
   1. I have created a chart that contains both line and scatter series objects.
   2. The x-axis is of type "category".
   3. The filterMode of the dataZoom feature is set to "none" in order to 
prevent the line from disappearing if only one point of the line is in view 
after zooming.
   4. Zoom in with the dataZoom feature in such a way that only one tick of the 
x-axis but the entire range of the y-axis is in view.
   
   Following picture shows the chart before zooming in:
   
![image](https://user-images.githubusercontent.com/5834134/160074666-1729eaa1-7809-40b8-800a-99789fc8d08e.png)
   
   
   ### Current Behavior
   
   After zooming in as described in step 4, the data of the other ticks is 
plotted at the same x-position (see picture below). 
   
![image](https://user-images.githubusercontent.com/5834134/160074555-9f9b1092-312a-44c8-86c7-e3949d29acb0.png)
   
   
   ### Expected Behavior
   
   After zooming in as described in step 4, only the data in view should be 
plotted at the correct position (as when filterMode is not set to "none").
   
![image](https://user-images.githubusercontent.com/5834134/160075006-762193bb-c010-4013-9d57-d56614ecb148.png)
   
   
   ### Environment
   
   ```markdown
   - OS: Windows 10
   - Browser: Google Chrome 99.0.4844.51
   - Framework: React 17.0.2
   ```
   
   
   ### Any additional comments?
   
   _No response_


-- 
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]

Reply via email to