Repository navigation
fix(visualMap): handle label collides with horizontal size visualMap - #20249
Conversation
|
Thanks for your contribution! |
|
The changes brought by this PR can be previewed at: https://echarts.apache.org/examples/editor?version=PR-20249@dd131a0 |
|
Better review the test file changes with the ignore of the whitespace enabled (refactor affected the indentations). |
|
@Ovilia is there anything more I should do, or anyone I should consult with regarding these changes? |
Ovilia
left a comment
There was a problem hiding this comment.
We sincerely appreciate your valuable contributions! We are currently running a special promotion for users who submit a Pull Request between September 25, 2024, and December 31, 2024. Eligible participants will receive a two-year enterprise membership to Baidu Comate, valued at 2000 RMB (approximately 285 USD).
To learn more about this product, please visit https://comate.baidu.com/. If you are interested in this offer, kindly send an email with the link to your Pull Request along with your Comate username and email address to ovilia@apache.org to claim your membership.
Thank you once again for your support!
|
Congratulations! Your PR has been merged. Thanks for your contribution! π |




Brief Information
This pull request is in the type of:
What does this PR do?
It switches visualMap handle label vertical align property basing on the visual map orientation and layout.
Fixed issues
Details
Before: What was the problem?
Label for handle at minimum position collides with the handle. The reason is that the distance between label and handle is based on the handle size and it changes depending on handle position. Currently label has always verticalAlign set to "middle", which is the cause of the collision (when distance is less than the half of the label height, the items collide). For labels below, vertical align could be "top" and for labels above, vertical align could be "bottom".
After: How does it behave after the fixing?
The labels below maximum range in horizontal visualMap get a slight offset to avoid collision.
This solution is not perfect, as the calculation method is different for vertical and horizontal visualMap, but I see no better way for now, to both fix the issue and keep other labels positions unchanged.
Document Info
One of the following should be checked.
Misc
ZRender Changes
Related test cases or examples to use the new APIs
Others
Merging options
Other information