-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Uncaught container is not an object" after layout is sent to newPlot #3350
Comments
This must be a side-effect of #3276 - where we deprecated More generally, if you (1) Oh well, we should still try to fix this thing. |
also note that var layout = {
title: "title",
margin: {l: 30, r: 50, t: 30, b: 10}
};
var data = [{
y: [1, 2, 1]
}]
Plotly.newPlot('graph', data, layout, {displayModeBar: false});
console.log(layout)
layout.margin = {}
layout.title.text = "edit title"
Plotly.update('graph', data, layout) works as expected. |
as well as: var layout = {
title: "title",
margin: {l: 30, r: 50, t: 30, b: 10}
};
var data = [{
y: [1, 2, 1]
}]
Plotly.newPlot('graph', data, layout, {displayModeBar: false});
console.log(layout);
layout.margin = {};
layout.title = "edit title";
Plotly.react('graph', data, layout) |
@etpinard Ended up with the react instead, not seeing any changes on performance though. Well, it does not matter. Closing this thread. |
When editing the layout object after it was sent it to
Plotly.newPlot
, it causes an error logUncaught container is not an object
.Seems only for non-objects that causes it:
Before version
1.43.0
the above code works.https://codepen.io/poldz123/pen/pqNBzj?editors=0010
The text was updated successfully, but these errors were encountered: