Workaround for wrong menu position when clicking on ... next to a segment #7680
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
…ment; also enlarge the clickable area for a segment item
hotzenklotz
approved these changes
Mar 11, 2024
Member
hotzenklotz
left a comment
hotzenklotz
left a comment
There was a problem hiding this comment.
Great find! Thank you so much.
Works as expected.
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.
Also, enlarge the clickable area for a segment item.
When react-component/trigger#447 has bubbled through to antd, we can remove the
alignPoint={false}part again.URL of deployed dev instance (used for testing):
Steps to test:
Issues: