Invalid array length when dragging component onto canvas

Question

Not sure why, But all of a sudden, when I start dragging components onto a canvas, I get this: This seems to happen when I edit a template, save it, and reload it. It also seems to happen when I try to drag a new component to the LAST element of the page; if I try to drag and element inside of a DIV container inside the template, it's fine. But if I try to drag it at the beginning of the template, I get the duplicate items I referenced in #2494 . I have a feeling this is related; somewhere ther...

andrewryan1906 · Accepted Answer

Here's another clue... once the canvas "breaks" (which I can reliable make happen by refreshing the page and forcing a load... this behavior doesn't happen on new templates, only when the template is loaded from my custom storage, but I verified the JSON hasn't been corrupted), if I take a component and drag it over the canvas, it creates "ghost" copies of the component, even though I haven't dropped it. Every time I hover to the top of the canvas, a new ghost component is created - again, even...

andrewryan1906 · Answer

OK, I managed to stick grapes.js into my Angular project and reference it instead of the minified version, so I could get more insight into what is going on. The problem seems to be in Sorter.js. The findPosition method is tasked with figuring out which element the cursor is hovering over. For some reason, this line of code: Is coming back NaN. This is tricking all the way through the code and causing an invalid array length. When I look at the dims, which is a two dimensional array with all of...

Invalid array length when dragging component onto canvas

Question

Answers (2)

Related Questions and Answers

How does the property color changes to blue when value changed?

Prevent <TABLE>from being modified during saving.

Component model is not reset when create new drag

FEAT: Disable <table> being auto amended during save

Paid Plugins That Match This Issue

Browse Plugin Categories