You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
On the Driver Career Stats page, the tooltip in the position/points chart displays value undefined for position if the driver has more than 50-60 races. For drivers under 50-60 races (51 is as closest as I can get to a cutoff) it displays properly.
Strangely, if you go to /drivers/max_verstappen, for example, some of the values display properly, whereas others do not.
This issue has already been created in the Chart.js repository (see below). It seems to be linked with the use of category as the y-axis type.
To Reproduce
Steps to reproduce the behavior:
Go to any driver's /driver/:driverId page who has more than 50-60 races
Hover over the chart to display the tooltip
See "Position: undefined"
Expected behavior
It should display the position value!
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Bug has been reported in Chart.js repository back in August: chartjs/Chart.js#5708
The text was updated successfully, but these errors were encountered:
Describe the bug
On the Driver Career Stats page, the tooltip in the position/points chart displays value
undefined
forposition
if the driver has more than 50-60 races. For drivers under 50-60 races (51 is as closest as I can get to a cutoff) it displays properly.Strangely, if you go to
/drivers/max_verstappen
, for example, some of the values display properly, whereas others do not.This issue has already been created in the Chart.js repository (see below). It seems to be linked with the use of
category
as the y-axis type.To Reproduce
Steps to reproduce the behavior:
/driver/:driverId
page who has more than 50-60 racesExpected behavior
It should display the position value!
Screenshots



If applicable, add screenshots to help explain your problem.
Additional context
Bug has been reported in Chart.js repository back in August: chartjs/Chart.js#5708
The text was updated successfully, but these errors were encountered: