Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Excessive padding after updating to v3 when using `pointHoverRadius` and `borderWidth`

See original GitHub issue

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

Issue Analytics

State:
Created a year ago
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

LeeLenaleeecommented, Jun 3, 2022

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

0reactions

LeeLenaleeecommented, Oct 11, 2022

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