UI slowing down with many neo fields and child blocks. about craft-neo HOT 5 CLOSED

I know what you mean. Unfortunately I don't think there's a whole lot I can do about it. The bulk of the HTML comes from Craft generating fields, and all that HTML is bound to slow down the UI. Large Matrix fields suffer the same problem, though Neo comes with some extra features that do affect performance a little more.

I've built some large Neo fields and while I've experienced some slow-down, they still perform well enough that it isn't a problem. I don't know how bad it is for you, but if it's unusable then there's probably something wrong.

from craft-neo.

Definitely usable, so not really a problem other than being slightly annoying. I think I read somewhere that they're updating the UI quite a bit for the next major release, hopefully that sorts it all out... Awesome plugin btw. :)

from craft-neo.

(#87) I don't know if this is the cause for anyone else, but I just discovered something that has a serious performance degradation effect with Neo – Rich text fields with fixed toolbars. If rich text fields inside Neo blocks have their fields fix to the top of the browser when scrolling, if this is triggered enough times it causes a huge UI performance hit. That said it's probably an issue even outside of Neo, but the situation would present itself more often with Neo.

This actually indicates a memory leak issue with Redactor, where events are probably not unbinding and piling up on top of each other. I'll have to submit a bug report with them, but in the meantime you'll just need to disable the fixed toolbar in your Redactor configs – "toolbarFixed": false

from craft-neo.

Any progress on this one? The more child blocks the slower it runs.

from craft-neo.

Closing this issue due to its age and inactivity since the release of Neo for Craft 3. If anyone has any issues with the speed of the UI with Neo and Craft 3, please feel free to open a new issue.

from craft-neo.