1455139 - Debugger shows Invalid callback argument with graph.js library

Status: RESOLVED WONTFIX

(DevTools :: Debugger, defect)

Description

[cdalxndr]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180323154952

Steps to reproduce:

Debugging and exploring variables at a breakpoint


Actual results:

Debugger reports variable as 'undefined', but 'console.log(variable)' works fine, and Edge browser debugger reports variable value fine.


Expected results:

Debugger should have shown correct variable value.

Comment 1

[cdalxndr]

More info at: https://github.com/chartjs/Chart.js/issues/5426#event-1582523398

Comment 2

[Jason Laster [:jlast]]

Chart.js 2.7.2.
Firefox 59.0.2(64-bit).

Using firefox debugger, the callback function has undefined 'values' variable.
This may be a Firefox specific bug because in Edge browser issue doesn't replicate:
When stopping inside the callback function, I ran the following commands in console:

>>values
function ()
>>values()
TypeError: can't convert undefined to object
>>values[0]
undefined
>>values.length
0

The unusual part is that going up in the stacktrace, to "tickFormatFunction" and checking the "ticks" variable it reports fine:

>>ticks
[…]
0: Object { value: 1454277600000, major: true }
1: Object { value: 1456783200000, major: true }
length: 2
__proto__: Array []

The stacktrace is:

callback (MyScript.js#260)
tickFormatFunction (Chart.bundle.js#18822)
convertTicksToLabels (Chart.bundle.js#18830)
update (Chart.bundle.js#11788)
update (Chart.bundle.js#18644)
getMinimumBoxSize (Chart.bundle.js#10951)
each (Chart.bundle.js#14434)
update (Chart.bundle.js#10965)
updateLayout (Chart.bundle.js#8794)
update (Chart.bundle.js#8749)
construct (Chart.bundle.js#8479)
Chart (Chart.bundle.js#10750)
setChartData (MyScript.js#227)
setData (MyScript.js#195)
loadData (MyScript.js#186)
i (jquery-3.2.1.slim.min.js#2)
fireWith (jquery-3.2.1.slim.min.js#2)
b[0] (jquery-3.2.1.slim.min.js#2)
ajax (product.html#389)

Comment 3

[Jason Laster [:jlast]]

Does this still happen for you?

Comment 4

[cdalxndr]

I'm too lazy to re-setup the environment and investigate if the issue still reproduces.
Hopefully, the original info I provided will allow you to replicate it.