Version
4.8.0
Reproduction link
https://jsfiddle.net/dalzell99/tyjzwdcg/1/
Steps to reproduce
Move the graph so the bar series is outside the graph window
What is expected?
The date range of the graph window doesn't change unexpectedly
What is actually happening?
The date range of the graph window increases to be about 5 times the expected range and the line series data is only shown in the middle 20% of the graph window
Edit: 14th Aug 10:30am (UTC+12)
It has something to do with the width of the bars as in the past we were able to fix the issue by setting barMaxWidth to 5% for the bar series.
Below are some screenshots showing the date range of the graph window changing. The line series data is exactly the same and datazoom date range at the bottom is also exactly the same.
Hourly - https://ibb.co/4WRZv2T
Shows hourly rainfall with 0 values in between the bars shown.
Daily - https://ibb.co/4mxwYND
Shows daily rainfall with no 0 values in bar series. The date range of the graph window expanded slightly compared to the hourly.
Weekly - https://ibb.co/7t3LgWR
Shows weekly rainfall with only one data point in series. The date range of the graph window has expanded significantly without the datazoom date range being changed.
3条答案
按热度按时间yi0zb3m41#
Hi! We've received your issue and please be patient to get responded. 🎉
The average response time is expected to be within one day for weekdays.
In the meanwhile, please make sure that you have posted enough image to demo your request. You may also check out the API and chart option to get the answer.
If you don't get helped for a long time (over a week) or have an urgent question to ask, you may also send an email to dev@echarts.apache.org . Please attach the issue link if it's a technical questions.
If you are interested in the project, you may also subscribe our mail list .
Have a nice day! 🍵
2nc8po8w2#
It seams can be resolved temporarily by set
dataZoom.filterMode: 'none'
rather thandataZoom.filterMode: 'weakFilter'
.The bug in 'weakFilter' needs to be fixed.
ki1q1bka3#
This issue is labeled with
priority: high
, which means it's a frequently asked problem and we will fix it ASAP.