You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to #490, this happens very easily when selecting a point near the middle of the graph and returning customHTML (in the chart options) that results in a tooltip that's slightly wider than the default. However, in this case, it's because the "left" CSS property is a negative amount.
Maybe by default "left" (or even "top") should not be negative, or if that will break something, then there can be additional flags to prevent "left" (or even "top") from going to a negative integer.
I agree that it looks correct in yours.
Could it be because of a difference in browser or OS?
I'm using "Google Chrome 120.0.6099.227 (Official Build) (64-bit)" in Windows 10.
Name
W Diu
Are you an IBM employee?
What happened?
Similar to #490, this happens very easily when selecting a point near the middle of the graph and returning customHTML (in the chart options) that results in a tooltip that's slightly wider than the default. However, in this case, it's because the "left" CSS property is a negative amount.
Maybe by default "left" (or even "top") should not be negative, or if that will break something, then there can be additional flags to prevent "left" (or even "top") from going to a negative integer.
This can also be reproduced by the example provided here: https://charts.carbondesignsystem.com/react/?path=/story/simple-charts-area-simple--area-time-series. Simply resize the window as shown in the screenshot and observe the left side is cut off when the tooltip could have been positioned to the right to avoid getting cut off.
Version
1.13.18
Data & options used
Relevant log output
No response
Codesandbox example
https://charts.carbondesignsystem.com/react/?path=/story/simple-charts-area-simple--area-time-series
What priority level would this be in your opinion?
P2
The text was updated successfully, but these errors were encountered: