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
JayWebz opened this issue
May 20, 2021
· 6 comments
Labels
BlockedIdentifies a task that is stuck due to a limitation beyond dev controlbugSomething isn't workingusabilityImprovements to usability of existing features
Was able to post on their forum. Apparently UCSD email doesn't like the reset password email that comes from canvasjs. I re-registered with a gmail address and had no problem. I was able to post in the chat asking if the issue has any priority at this stage and expressing what the expected behavior should be. https://canvasjs.com/forums/topic/problem-zooming-to-the-end-of-a-chart/page/2/#post-34380.
canvasjs doesn't have a public github repo and all chat is funneled through their website forum.
Mouse events are captured only when mouse is on top of the chart. Any mouse event fired outside of the chart cannot be captured. Hence, it is not possible to trigger the zoom when mouse event is fired out of the chart as of now.
However, we will reconsider this behavior in future releases.
Going to suggest if an optional function can be passed into canvas js that contains the event listener so that the context outside of the react component is understood.
Currently, the chart component has its own zoom and pan functionality, and cannot consume any events fired from a parent component that could trigger the zoom event.
JayWebz
added
the
Blocked
Identifies a task that is stuck due to a limitation beyond dev control
label
Oct 25, 2021
BlockedIdentifies a task that is stuck due to a limitation beyond dev controlbugSomething isn't workingusabilityImprovements to usability of existing features
History
From #187 -
Goal
Remove current padding solution entirely, allow for zoomed range to be visible when dragging mouse beyond confines of the visual component.
Steps
Short-term Solutions
The text was updated successfully, but these errors were encountered: