Clipping can be confusing and ugly

[chrisbolin]

For a few reasons, clipping can be confusing to users:

• It doesn't happen to all graphs (only containers that need clipping, like Zoom)
• It can cut off half or even 75% off a data point. Scatter points that are extrema in both x and y are 3/4th hidden. The first and last bars in a bar graph look strangely skinny.
• domainPadding works well for some cases, but because it (rightfully) aims to not add quadrants, it can't help points where x or y is 0.

When the graph line gets near the top of the graph and sits on the very top of the graph, half the line appears to be hidden making it tough to see the top of the line.

• from https://github.com/FormidableLabs/victory-native/issues/83

Any thoughts on how we might address this @boygirl?

[becca-bailey]

I ran into some of this confusion myself when building a Canvas line component. Most of my other canvas components worked automatically with the data interpolation, but it was a bit confusing to figure out how to use a clip container to animate the VictoryLine data component, and I ended up with a pretty hacky solution. I'm going to +1 this and keep this issue open for us to consider.

[becca-bailey]

I'm going to convert this to a discussion so we can continue to discuss options for improving this behavior.

[chriszrc]

@becca-bailey I'm here because for scatter charts, the domainPadding on x axis does nothing, and I'm looking for a way to not have the scatter points near 0 overlap the axis:

https://codesandbox.io/p/sandbox/victory-typescript-scatter-chart-ytq5w9?file=%2Fsrc%2FComponents%2FGraph.tsx%3A8%2C1-11%2C1

[carbonrobot]

Confirmed a bug with VictoryScatter, opened an issue here. #2690