Thank you for elaborating on this.
Indeed we were able to reproduce the problematic behavior in our local tests now and we have forwarded it to our developers for further review. We will do our best to address this issue for the next weekly internal build (scheduled for tomorrow) -- for the time being as a workaround we would suggest you to set the AxisX.Visibility to "Visible".
Sorry for the temporary inconvenience.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items.