I have a probably not common issue, but also probably easy to fix. I have also posted it in the community, and I reproduce it here.
I have a plot (that I create with Python but I edit later on the html/js) that looks like this:
When I open the html, there are errors on the console:
Error: Problem parsing d="MNaN,NaNHNaNMNaN,NaNHNaN"
Error: Problem parsing d="MNaN,NaNHNaNMNaN,NaNHNaN"
Although the graphs look fine, these errors are annoying (as there are many graphs like this on the page, and therefore many errors).
(I have tested many versions 2.XX and it always happen, including 2.14.0).
Also, what seems to be causing this is related to the black line of xaxis2 and yaxis2 (which is the top-right graph). This is how the layout looks like for this part:
If I comment out the linecolor: "black", the errors disappear.
I have created a (somewhat) minimal example here: https://codepen.io/filipesmg/pen/ZExmorL
However, the error is not showing directly in codepen (maybe because the error is inside plotly.js?) If that code is put inside <html>(...)</html>, it shows up. The linecolor lines are 640 and 652.
Investigating the plotly.min.js file while running the code, I noticed that the error comes from this part:
(Y.attr = function (e, r) {
if (arguments.length < 2) {
(...)
}
return this.each(K(e, r));
}),
which calls the function K(e,r) that has:
function(){this.setAttribute(e,r)}}
The problem is that in my example, at some point there seems to be no argument to the function (e,r), and r is undefined. There are many times where arguments.length = 1 or 2, but there are 2 times where it is undefined. In these cases, it doesn't enter the if (arguments.length < 2) and it goes to return this.each(K(e, r)); where it gives an error in the .setAttribute(e,r). Maybe a simple if ( ! r) { return; } would solve the issue, but I can't follow more the code to know if it'd affect other things.
I'm using 12.3.1, and I this error shows up in Safari 15.4 and in Chrome 104.0.5112.79, but not on Firefox 103.0.2.
I have a probably not common issue, but also probably easy to fix. I have also posted it in the community, and I reproduce it here.
I have a plot (that I create with Python but I edit later on the html/js) that looks like this:
When I open the html, there are errors on the console:
Although the graphs look fine, these errors are annoying (as there are many graphs like this on the page, and therefore many errors). (I have tested many versions 2.XX and it always happen, including 2.14.0). Also, what seems to be causing this is related to the black line of
xaxis2
andyaxis2
(which is the top-right graph). This is how the layout looks like for this part:If I comment out the
linecolor: "black"
, the errors disappear.I have created a (somewhat) minimal example here: https://codepen.io/filipesmg/pen/ZExmorL However, the error is not showing directly in codepen (maybe because the error is inside plotly.js?) If that code is put inside
<html>(...)</html>
, it shows up. Thelinecolor
lines are 640 and 652.Investigating the plotly.min.js file while running the code, I noticed that the error comes from this part:
which calls the
function K(e,r)
that has:The problem is that in my example, at some point there seems to be no argument to the
function (e,r)
, andr
isundefined
. There are many times wherearguments.length = 1
or2
, but there are 2 times where it isundefined
. In these cases, it doesn't enter theif (arguments.length < 2)
and it goes toreturn this.each(K(e, r));
where it gives an error in the.setAttribute(e,r)
. Maybe a simpleif ( ! r) { return; }
would solve the issue, but I can't follow more the code to know if it'd affect other things.I'm using 12.3.1, and I this error shows up in Safari 15.4 and in Chrome 104.0.5112.79, but not on Firefox 103.0.2.