[Bug] : candlestick and bar chart ticks and split lines with xAxis of type time are not aligned
- Dominant language
- TypeScript
- Stars
- 67.3k
- Forks
- 19.8k
- Avg merge
- 11d 14h
- Merged PRs (30d)
- 8
Description
### Version
5.4.1
### Link to Minimal Reproduction
https://jsfiddle.net/7n6v38em/
### Steps to Reproduce
1. create two grids one for the candlestick series, and the other for the bar series.
2. xAxis is of type 'time' for both , and yAxis is default of type 'value'
3. the datasource is the same for both.. the candlestick is using open,close,low,high dimensions, and the bar chart is using 'volume' dimension
### Current Behavior
the split and tick lines are not aligned between the candlestick and bar charts.
please check and run the fiddle
- Notice that the upper grid vertical split lines do NOT align to the bottom grid vertical split lines
- also notice that the axisPointer line is not a straight line between both the grids.
- also notice that the first bar on the bottom grid starting point is aligned to the left edge of the grid whereas the candlestick first candle is overflowing outside of the left edge
### Expected Behavior
the split and tick lines should align perfectly to each other because the series data is the same, and the xAxis type is the same being 'time'.. this is an issue because the same item should be vertically aligned with one another. The candlestick candles should align perfectly to the volume bars for each tick, ticks should align, and split lines should align in straight line.
This behavior works as expected if we change the xAxis type from 'time' to 'category'. The problem though with using 'category' is that all formatting of the data has to be done manually, and also 'category' type does not support boundaryGap with a percentage which we require.
### Environment
```markdown
- OS:
- Browser:
- Framework:
```
### Any additional comments?
change the xAxis type for both to 'category' and notice the difference. In this case both the grid split lines and ticks align perfectly.. however, we do not want to be forced to use 'category' because it requires us to do lots of manual formatting of labels, etc. also category does not support boundaryGap with a percentage on both sides which is important for us.
Kindly let us know if there is a solution or this is a bug
Contributor guide
Assessment
This issue has not been assessed yet.