elasticX(true) on Composite breaks rangeChart zooming

[eteubert]

If elasticX(true) is enabled on a composite chart, connected to a rangeChart, it breaks rangeChart zooming. Setting elasticX(false) "fixes" the behavior.

The bug first occurs in beta.9.

jsfiddle: https://jsfiddle.net/ocxxuyL5/1/

[alan-unravel]

Okay so beta.9 pushed the elasticX() from the parent chart down to it's children. As you can see here focus will be ignored if elasticX is set to true.
So essentially your initial behaviour got through a loophole it seems. @gordonwoodhull can you confirm if this was intended?

[eteubert]

Ah ok that makes sense. It should just be mentioned in the API docs. And/or setting elasticX on composite charts should not be available then, or generate an error.

[alan-unravel]

We could probably generate a warning of some sort and it should definitely be in the docs. I don't see why it would be disabled though since some people use composite charts without range charts.

[gordonwoodhull]

I don't understand. What's the use case for a focus chart with elasticX? Its domain will always be set by the range chart.

Or alternately, is there a use case where some of the subcharts are elasticX but others are not? Don't they always share the X axis?

I think I must be missing something here.

[alan-unravel]

I think you are right, I can't really think of a use-case.

[gordonwoodhull]

I guess it could be useful to have the first render use elasticX, and then subsequently just get the domain from the range chart.

[gordonwoodhull]

Okay, I'll consider this a documentation issue: the fact that elasticX will disable the range/focus feature is mentioned only in .focus(), not in .rangeChart() or .elasticX() and it should be mentioned those places.