Excessive padding after updating to v3 when using pointHoverRadius and borderWidth

[arggh]

Expected behavior

I would expect layout.padding = 0 to actually make padding 0.

Current behavior

When dataset uses pointHoverRadius and borderWidth, the padding is dramatically increased regardless of any padding settings. It can easily be seen that there's no reason to include that extra padding, as everything would easily fit on the canvas without any extra padding. Especially on mobile, this creates a very silly user experience.

The same effect, but with less dramatic outcome, can be observer when using pointHoverRadius and pointRadius.

Reproducible sample

https://codepen.io/arggh/pen/JjpZJYG

Optional extra steps/info to reproduce

No response

Possible solution

No response

Context

No response

chart.js version

v3.8.0

Browser name and version

Chrome 101

Link to your project

No response

[LeeLenaleee]

https://www.chartjs.org/docs/latest/configuration/layout.html

[arggh]

https://www.chartjs.org/docs/latest/configuration/layout.html

Setting autoPadding: false seems to remove the padding, but do @LeeLenaleee agree, that in the repro there's excessive padding around the chart?

Apply automatic padding so visible elements are completely drawn.

In the repro, there's a padding of about 40 pixels on both sides, with nothing drawn on the padded area.

[LeeLenaleee]

Seems to happen because of a configuration mistake.
The borderWidth is supposed to be a number. But you supplied it as a string.
This is not supported, if you supply it as a number it shows the chart normally fine

[arggh]

The borderWidth is supposed to be a number. But you supplied it as a string.

🤦‍♂️ You are very much correct. Thank you for noticing, problem solved.

[kurkle]

Jacco van den Berg kirjoitti 03.06.2022 11:23:

https://www.chartjs.org/docs/latest/configuration/layout.html

Looks like autoPadding is missing from migration guide. Also the pen in the issue has `borderWidth: '2'`, which I believe is used in a calculation of the padding as string (something line 8 + '2', ending up being `'82'`) or something.

[LeeLenaleee]

The autopadding was added in 3.6 as an enhancement (#9716) so it does not need to be in the migration guide since it was not breaking and was not between 2 major versions