fix(dataZoom): fix dataZoom for single data #21043
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The changes brought by this PR can be previewed at: https://echarts.apache.org/examples/editor?version=PR-21043@f5c8bf6 |
100pah
approved these changes
Jun 19, 2025
|
Congratulations! Your PR has been merged. Thanks for your contribution! 👍 |
Ovilia
added
PR: doc unchanged
PR: supplementary
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Brief Information
This pull request is in the type of:
What does this PR do?
#16978 brings a bug for single data with dataZoom, where
data.count()is 1 andconst step = thisShadowExtent[1] / (data.count() - 1);beingInfinityand the dataZoom is displayed at an unexpected position.Fixed issues
Details
Before: What was the problem?
DataZoom is displayed at an unexpected position.
After: How does it behave after the fixing?
DataZoom is displayed at the same position as 5.6.0
Document Info
One of the following should be checked.
Misc
ZRender Changes
Related test cases or examples to use the new APIs
N.A.
Others
Merging options
Other information
TODO: axes other than time axes still have the problem of being not the same as the data shape, which should be improved in future versions.