Describe the issue
When the different parts of the axis are rendered we first check if it is necessary to render each part. For example a line of width 0 is not necessary to render. However, this causes problems for users when attempting to set the padding forcing them to fudge the rendering just to add the padding.
There are several usages in kibana of users forcing these styles:
const style = {
tickLine: { size: 0.0001, padding: 4, visible: true },
}
To Reproduce
Steps to reproduce the behavior:
- Go to this story
- Set any of the axis
tickLine sizes to 0
- Notice the entire line, including padding, is removed from rendering
Expected behaviour
The rendering of axes properties should be solely driven by the visible prop.
Screenshots

Describe the issue
When the different parts of the axis are rendered we first check if it is necessary to render each part. For example a line of width
0is not necessary to render. However, this causes problems for users when attempting to set the padding forcing them to fudge the rendering just to add the padding.There are several usages in kibana of users forcing these styles:
data_preview_chart.tsxmultilayer_timeaxisTo Reproduce
Steps to reproduce the behavior:
tickLinesizes to0Expected behaviour
The rendering of axes properties should be solely driven by the
visibleprop.Screenshots
