bugfix: tooltip content placement#1967
Open
Algoritm211 wants to merge 1 commit intoswimlane:masterfrom
Open
Conversation
Algoritm211
force-pushed
the
bugfix/ngx-chart-content-left-position
branch
from
eccebde to
3a1e549
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
Initial bug - #1640 . Unfortunately, now when using a custom
tooltipTemplatein a vertical bar chart, the left most bar's tooltip is not calculated correctly and can be clipped based on template content.What is the new behavior?
This is a solution for #1640. Now tooltip's content won't be outside the screen and will be always in viewport. The tooltip position is automatically adjusted for maximum visibility aligning with left corner
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: